From: Petr Baudis <pasky@suse.cz>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)?
Date: Fri, 29 Jul 2005 13:13:04 +0200 [thread overview]
Message-ID: <20050729111304.GS24895@pasky.ji.cz> (raw)
In-Reply-To: <Pine.LNX.4.58.0507291254100.5849@wgmdd8.biozentrum.uni-wuerzburg.de>
Dear diary, on Fri, Jul 29, 2005 at 12:57:50PM CEST, I got a letter
where Johannes Schindelin <Johannes.Schindelin@gmx.de> told me that...
> Hi,
Hello,
> On Fri, 29 Jul 2005, Petr Baudis wrote:
>
> > You might get the push access rather lately in the process (this "lazy
> > development privileges granting" is one of the point of distributed
> > VCSes), at point where other people are used to pull from you and
> > renaming your branch locally might mean some trouble.
>
> I still do not get it. What is so wrong with
>
> git-switch-tree remotehead
> git-merge master
> git-push remoteside remotehead
>
> which would have the further advantage of documenting what you really did
> in the history.
How would that document anything normal push wouldn't?
> And if you really want to be able to spread chaos in your own head, you
> can do something like
>
> ln -s master .git/refs/heads/remotehead
> git-push remoteside remotehead
I'd argue that's much more messy and evil than pushing to heads with
different names. If you compare what you just proposed with pushing to
heads with different names, what's the advantage?
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone. -- Alan Cox
next prev parent reply other threads:[~2005-07-29 11:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 12:58 How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)? Josef Weidendorfer
2005-07-28 1:32 ` Junio C Hamano
2005-07-28 12:08 ` Petr Baudis
2005-07-28 13:07 ` Johannes Schindelin
2005-07-28 15:35 ` Petr Baudis
2005-07-28 15:56 ` Johannes Schindelin
2005-07-28 16:18 ` Petr Baudis
2005-07-28 16:52 ` Junio C Hamano
2005-07-28 17:32 ` Johannes Schindelin
2005-07-28 18:45 ` Ryan Anderson
2005-07-28 18:51 ` Johannes Schindelin
2005-07-28 18:39 ` Petr Baudis
2005-07-28 18:49 ` Johannes Schindelin
2005-07-28 19:47 ` Matthias Urlichs
2005-07-28 20:14 ` Johannes Schindelin
2005-07-29 7:11 ` Petr Baudis
2005-07-29 2:24 ` Junio C Hamano
2005-07-29 7:06 ` Petr Baudis
2005-07-29 7:48 ` Junio C Hamano
2005-07-29 8:10 ` Petr Baudis
2005-07-29 8:54 ` Junio C Hamano
2005-07-29 9:40 ` Petr Baudis
2005-07-29 10:57 ` Johannes Schindelin
2005-07-29 11:13 ` Petr Baudis [this message]
2005-07-29 12:26 ` Johannes Schindelin
2005-07-29 12:28 ` Petr Baudis
2005-07-30 2:11 ` Junio C Hamano
2005-07-29 20:40 ` Matthias Urlichs
2005-07-30 22:16 ` Junio C Hamano
2005-08-13 4:11 ` Carl Baldwin
2005-08-13 7:48 ` Junio C Hamano
2005-08-15 16:23 ` Carl Baldwin
2005-08-15 23:55 ` Johannes Schindelin
2005-07-29 9:10 ` Josef Weidendorfer
2005-07-28 21:13 ` Matthias Urlichs
2005-07-29 7:14 ` Petr Baudis
2005-07-28 18:53 ` Josef Weidendorfer
2005-07-28 19:19 ` Unnamed branches Petr Baudis
2005-07-28 16:14 ` How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)? Junio C Hamano
2005-07-28 16:23 ` Petr Baudis
2005-07-28 15:35 ` Petr Baudis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050729111304.GS24895@pasky.ji.cz \
--to=pasky@suse.cz \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox