From: Steffen Prohaska <prohaska@zib.de>
To: Jan Hudec <bulb@ucw.cz>
Cc: Junio C Hamano <gitster@pobox.com>,
Pierre Habouzit <madcoder@debian.org>,
git@vger.kernel.org
Subject: Re: git push (mis ?)behavior
Date: Tue, 9 Oct 2007 09:23:42 +0200 [thread overview]
Message-ID: <5C3443FD-DEC3-4EDC-B10B-0C4307EF9492@zib.de> (raw)
In-Reply-To: <20071009050533.GA2968@efreet.light.src>
On Oct 9, 2007, at 7:05 AM, Jan Hudec wrote:
> On Fri, Sep 28, 2007 at 00:07:27 -0700, Junio C Hamano wrote:
>> Steffen Prohaska <prohaska@zib.de> writes:
>>
>>> When "remote.<name>.push" is set I'd expect "git push" to
>>> choose only the 'right' remote.<name>.push lines, that is
>>> the lines that have the current branch as the local ref.
>
> I would like this for another reason and maybe in slightly
> different way.
> Basically I would have configured something along the lines:
> [remote "origin"]
> push = refs/heads/*:refs/heads/jahu/*
> and would want to choose, via option, whether I want to push all
> the branches
> or just the current one, but in any case with the renaming specified.
>
> The idea behind this is to have a shared repository, but not shared
> branches.
> Everybody would have a subdirectory in refs/heads where he could push
> anything that the others should see and than somebody else (either
> designated
> integrator, or just anybody different) would do a quick review and
> merge it
> into master.
>
> Now I could of course push out everything, but usually I'd want to
> push
> exactly the current branch, renaming it by the rule given, whether
> it already
> existed in origin or not. Than there can be eg. a post-receive hook
> notifying
> the integrator that there is something for review.
I had a similar scenario in mind. So a more general question is the
following:
Git well supports the clone from read-only and push to private repo
scheme.
In this case all repositories you're pushing to are by definition _your_
repositories. The only question left is, which subset of your
branches are
pushed. But there's no need for renaming during push.
Now the question is, what is a sensible workflow on a shared repository?
One option is to use some kind of private 'namespace' scheme. For
example
developers should push their topics to a branch prefixed with their
name,
or to a 'subdirectory' ref/heads/needsreview/*.
This workflow may require to 'rename' branches during push. So how
can this
be supported by git? Supporting only renames that add a prefix, as
suggested
by Jan, may be reasonable restriction.
Steffen
next prev parent reply other threads:[~2007-10-09 7:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 13:04 git push (mis ?)behavior Pierre Habouzit
2007-09-27 13:30 ` Wincent Colaiuta
2007-09-27 15:28 ` Benoit SIGOURE
2007-09-27 19:22 ` Junio C Hamano
2007-09-27 19:36 ` Pierre Habouzit
2007-09-28 6:52 ` Steffen Prohaska
2007-09-28 6:58 ` Pierre Habouzit
2007-09-28 9:26 ` Steffen Prohaska
2007-09-28 9:44 ` Junio C Hamano
2007-09-28 10:04 ` Steffen Prohaska
2007-09-28 7:07 ` Junio C Hamano
2007-09-28 9:11 ` Steffen Prohaska
2007-09-28 13:31 ` Johannes Schindelin
2007-10-09 5:05 ` Jan Hudec
2007-10-09 7:23 ` Steffen Prohaska [this message]
2007-09-28 12:38 ` Wincent Colaiuta
2007-10-03 5:10 ` Miles Bader
2007-10-03 5:39 ` Junio C Hamano
2007-10-03 6:47 ` Wincent Colaiuta
2007-10-03 8:32 ` Miles Bader
2007-10-03 7:35 ` Pierre Habouzit
2007-10-03 8:57 ` Miles Bader
2007-10-03 9:03 ` Pierre Habouzit
2007-10-03 10:25 ` Wincent Colaiuta
2007-10-03 10:49 ` Karl Hasselström
2007-10-03 11:08 ` Junio C Hamano
2007-10-03 11:22 ` Wincent Colaiuta
2007-10-03 13:14 ` Karl Hasselström
2007-10-03 15:27 ` Johannes Schindelin
2007-10-03 16:07 ` Karl Hasselström
2007-10-03 16:18 ` Johannes Schindelin
2007-10-03 16:28 ` Pierre Habouzit
2007-10-03 16:44 ` Johannes Schindelin
2007-10-03 17:02 ` Karl Hasselström
2007-10-04 14:47 ` Steffen Prohaska
2007-10-04 15:54 ` Wincent Colaiuta
2007-10-04 16:24 ` Steffen Prohaska
2007-10-04 17:49 ` Wincent Colaiuta
2007-10-03 16:26 ` Wincent Colaiuta
2007-10-03 11:10 ` Benoit SIGOURE
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5C3443FD-DEC3-4EDC-B10B-0C4307EF9492@zib.de \
--to=prohaska@zib.de \
--cc=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=madcoder@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).