From: Junio C Hamano <gitster@pobox.com>
To: David Soria Parra <sn_@gmx.net>
Cc: Rotem Yaari <vmalloc@gmail.com>, git@vger.kernel.org
Subject: Re: Feature Request: Branch Annotations
Date: Wed, 08 Oct 2008 16:12:26 -0700 [thread overview]
Message-ID: <7vwsgiptph.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <48ECB5CB.4010703@gmx.net> (David Soria Parra's message of "Wed, 08 Oct 2008 15:29:47 +0200")
David Soria Parra <sn_@gmx.net> writes:
>> Any opinions on this?
>
> would be great to have something like that build in git-core like
>
> git branch -i 'Fix bla' ds/fix next
> git branch -i
> ds/fix (Fix Bla)
Haven't people watched Linus on google tech talk? Here is an excerpt from
the transcript (http://git.or.cz/gitwiki/LinusTalk200705Transcript):
... well actually you shouldn't call it "test", you should basically
name your branches the way you name your functions, you should call
them something short and sweet and to the point -- What is that branch
doing.
IOW, why did you name the branch "ds/fix" and not "ds/fix-bla"?
next prev parent reply other threads:[~2008-10-08 23:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d2115f4f0810080341m27c4ca9bv9b1e9b66704ef3fa@mail.gmail.com>
[not found] ` <d2115f4f0810080348t62e18b14x1dfe798974332b05@mail.gmail.com>
2008-10-08 10:49 ` Feature Request: Branch Annotations Rotem Yaari
2008-10-08 10:55 ` Thomas Adam
2008-10-08 11:41 ` Baz
2008-10-08 12:08 ` Marc Weber
2008-10-08 13:29 ` David Soria Parra
2008-10-08 23:12 ` Junio C Hamano [this message]
2008-10-08 23:20 ` David Soria Parra
2008-10-08 23:21 ` Avery Pennarun
2008-10-09 0:20 ` Miklos Vajna
2008-10-10 8:24 ` Peter Krefting
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=7vwsgiptph.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sn_@gmx.net \
--cc=vmalloc@gmail.com \
/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).