From: Diego Novillo <dnovillo@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: [maint] Guidelines for experimental branches
Date: Wed, 05 Mar 2003 01:31:00 -0000 [thread overview]
Message-ID: <slrnb6ahkh.e93.dnovillo@tornado.toronto.redhat.com> (raw)
In-Reply-To: <3E648828.3080502@suse.cz>
In article <3E648828.3080502@suse.cz>, Michal Ludvig wrote:
> Andrew Cagney wrote:
>> +@item @var{owner}_@var{name}-@var{YYYYMMDD}-branchpoint
>> +@itemx @var{owner}_@var{name}-@var{YYYYMMDD}-branch
>> +The branch point and corresponding branch tag. @var{YYYYMMDD} is the
>> +date that the branch was created. A branch is created using the
>
> Is it necessary to have the date in the name of the branch? IMHO it's
> fine for the branchpoint, as well as for mergepoints, but for the branch
> itself it's useless. People could much better remember words than
> 8-digits chunks and having to look on the webpage everytime, when I want
> to check out a branch is boring.
>
If the branch is long lived, you may want to re-create it more than once
for performance reasons. As you get farther and farther from the
branchpoint, CVS operations get increasingly slower. If dates are too
long, you could also use 2-3 digit numbers.
Diego.
next prev parent reply other threads:[~2003-03-05 1:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 23:23 Andrew Cagney
2003-03-03 23:37 ` David Carlton
2003-03-04 0:09 ` Andrew Cagney
2003-03-04 4:19 ` Eli Zaretskii
2003-03-04 11:04 ` Michal Ludvig
2003-03-05 1:31 ` Diego Novillo [this message]
2003-03-05 10:32 ` Michal Ludvig
2003-03-05 15:14 ` Diego Novillo
2003-03-05 17:06 ` Andrew Cagney
2003-03-04 2:08 Michael Elizabeth Chastain
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=slrnb6ahkh.e93.dnovillo@tornado.toronto.redhat.com \
--to=dnovillo@redhat.com \
--cc=gdb@sources.redhat.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