From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFC] just an (stupid) idea when creating a new branch
Date: Sun, 09 Jul 2006 19:04:32 +0200 [thread overview]
Message-ID: <e8rcu5$je5$2@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.63.0607090011000.29667@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin wrote:
> On Sat, 8 Jul 2006, Jakub Narebski wrote:
>
>> moreau francis wrote:
>>
>>> Would it be possible to let the user stick a short explanation
>>> on what a branch is supposed to implement during its creation.
>>
>> It would be possible when/if branch and remotes config would migrate
>> to .git/config. Currently too many I think relies on refs/heads being
>> simple sha1 of "top" commit.
>
> But it does not need a change of existing practice at all! Just add the
> information provided by --topic as branch."pathname".description to the
> config. And make format-patch aware of that.
And make tools remove stale descriptions. I sometimes rename branches "by
hand", as currently there is I think no tool for this...
By the way, did this series of patches (adding support for branch and
remotes configuretion to config file) made into 'next', 'master' or even
'pu', or after some discussion it stalled?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-07-09 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 15:55 [RFC] just an (stupid) idea when creating a new branch moreau francis
2006-07-08 21:41 ` Jakub Narebski
2006-07-08 22:15 ` Johannes Schindelin
2006-07-09 17:04 ` Jakub Narebski [this message]
2006-07-09 19:09 ` Johannes Schindelin
2006-07-09 6:54 ` Marco Costalba
2006-07-09 14:33 ` Johannes Schindelin
2006-07-09 22:01 ` Petr Baudis
2006-07-09 22:12 ` Johannes Schindelin
2006-07-09 3:27 ` Pavel Roskin
2006-07-09 9:48 ` Re : " moreau francis
2006-07-09 10:16 ` Junio C Hamano
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='e8rcu5$je5$2@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).