Closed Bug 1186269 Opened 9 years ago Closed 9 years ago

create a new repository : hg.mozilla.org/SeaMonkey/tools

Categories

(Developer Services :: Mercurial: hg.mozilla.org, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ewong, Assigned: fubar)

References

Details

In hopes to consolidate all SeaMonkey releng repos under 
hg.mozilla.org/SeaMonkey, we would like to have a new repo
hg.mozilla.org/SeaMonkey/patchers (is this an ok name, Callek?)

It will house all our CVS-based patcher files (patcher-configs
and patcher files).
Flags: needinfo?(bugspam.Callek)
Having talked to :Callek over irc, while we do need a new repo, it won't
be only for the patchers.   we need it for our tool repository (which is
currently in Callek's user repo).  We'll be moving it under hg.mozilla.org/SeaMonkey called tools.

So:
hg.mozilla.org/SeaMonkey/tools
Flags: needinfo?(bugspam.Callek)
Summary: create a new repository : hg.mozilla.org/SeaMonkey/patcher → create a new repository : hg.mozilla.org/SeaMonkey/tools
Blocks: 1121281
Do you really need a separate repository? Why can't tools be checked into a tools/ (or similar) directory in the SeaMonkey repository?
(In reply to Gregory Szorc [:gps] from comment #2)
> Do you really need a separate repository? Why can't tools be checked into a
> tools/ (or similar) directory in the SeaMonkey repository?

What SeaMonkey repository are you referring to?
Greg, this is the seamonkey equivalent of build/tools. And currently resides in my user directory. This is as we discussed this week of a proper home for it
OK. Establishing a formal repo outside of Callek's user directory gets a big +1 from me.
So with gps' +1,  what next?
Flags: needinfo?(hwine)
What permissions should the repo have? Looks like you have both scm_level_2 and _3 under SeaMonkey/ currently. Any hooks?
Assignee: nobody → klibby
fubar, lets match build/tools with regard to hooks and level2.

For sake of completeness, when finalizing this repo can you enumerate both the global hooks and the repo-specific hooks that are enabled for this once complete?
Done: http://hg.mozilla.org/SeaMonkey/tools/

$ hg -R tools/ showconfig hooks
hooks.sorthooks=True
hooks.changegroup.recordlogs=/repo/hg/scripts/record-pushes.sh
hooks.changegroup.mirrorpush=/repo/hg/scripts/push-repo.sh
hooks.pushkey.mirrorpush=/repo/hg/scripts/push-repo.sh
hooks.pretxnchangegroup.single_root=python:mozhghooks.single_root.hook
hooks.changegroup.push_printurls=python:mozhghooks.push_printurls.hook
hooks.pretxnchangegroup.a_singlehead=/repo/hg/scripts/hg_require_single_head
hooks.pretxnchangegroup.pushlog=<function pretxnchangegrouphook at 0x1fbf230>

Shout if you want the hooks tweaked.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
(In reply to Kendall Libby [:fubar] from comment #9)
> Done: http://hg.mozilla.org/SeaMonkey/tools/
> 
> $ hg -R tools/ showconfig hooks
> hooks.sorthooks=True
> hooks.changegroup.recordlogs=/repo/hg/scripts/record-pushes.sh
> hooks.changegroup.mirrorpush=/repo/hg/scripts/push-repo.sh
> hooks.pushkey.mirrorpush=/repo/hg/scripts/push-repo.sh
> hooks.pretxnchangegroup.single_root=python:mozhghooks.single_root.hook
> hooks.changegroup.push_printurls=python:mozhghooks.push_printurls.hook
> hooks.pretxnchangegroup.a_singlehead=/repo/hg/scripts/hg_require_single_head
> hooks.pretxnchangegroup.pushlog=<function pretxnchangegrouphook at 0x1fbf230>
> 
> Shout if you want the hooks tweaked.

Thanks :fubar!
Flags: needinfo?(hwine)
You need to log in before you can comment on or make changes to this bug.