From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Status of git.git repository
Date: Fri, 5 Aug 2005 00:26:11 +0200 [thread overview]
Message-ID: <20050804222611.GE24479@pasky.ji.cz> (raw)
In-Reply-To: <7vhded6o0r.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Sat, Jul 30, 2005 at 04:11:48AM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> By the way, do people mind my posting my own patches to the
> list? I keep the same in the "pu" (proposed updates) branch, so
> if the list readers think I am just adding noise to the list
> traffic, I would stop doing so, and instead just invite
> interested people to browse the "pu" branch.
Browsing the "pu" branch may be bothersome and you won't ensure that the
related discussion stays in a single thread, and posting the patches
here makes them generally more visible, so I think it's a good idea to
keep doing so.
Cogito (and Git itself as well, I guess) does not handle those
"volatile" branches well at all - following them is difficult since
Cogito will think that you did some local commits and want to do a tree
merge. Would anyone consider doing
if ref(updatebranch) == ref(master) then
merge: always_fastforward
else
merge: perhaps_treemerge
a Bad Thing (tm)? It seems to me that it should do the right thing and
never get it wrong.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone. -- Alan Cox
prev parent reply other threads:[~2005-08-04 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 2:11 Status of git.git repository Junio C Hamano
2005-08-01 3:29 ` Horst von Brand
2005-08-04 22:26 ` Petr Baudis [this message]
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=20050804222611.GE24479@pasky.ji.cz \
--to=pasky@suse.cz \
--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