[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] do not ignore errors like ENOSPC, EIO when writing to stdout
From: |
Akim Demaille |
Subject: |
Re: [PATCH] do not ignore errors like ENOSPC, EIO when writing to stdout |
Date: |
Tue, 31 Jan 2012 10:05:35 +0100 |
Le 31 janv. 2012 à 09:57, Jim Meyering a écrit :
> Akim Demaille wrote:
>> Installed in branch-2.5.
>>
>> Is there some standard in the gnulib universe on the names to
>> give to the various branches? In Bison, master is the next major
>> release, and we use branch-X.Y for the maintenance branches, but
>> some version independent naming scheme would be fine.
>
> You might like to follow git.git's example. They use branches named
> after their function, rather than ones named after (imho)less-meaningful
> numbers.
>
> That seems more scalable in the long run:
>
> maint
> master
> next
> pu
> todo
>
> Otherwise, eventually you'll end up with many many branches,
> all but a few of which are inactive.
Thanks! Using these names, I found the gitworkflows man page!
(http://schacon.github.com/git/gitworkflows.html) That does
help understand what "pu" can mean (exercise left to the reader :)
- [PATCH] do not ignore errors like ENOSPC,EIO when writing to stdout, Jim Meyering, 2012/01/29
- Re: [PATCH] do not ignore errors like ENOSPC, EIO when writing to stdout, Akim Demaille, 2012/01/29
- Re: [PATCH] do not ignore errors like ENOSPC, EIO when writing to stdout, Jim Meyering, 2012/01/29
- Re: [PATCH] do not ignore errors like ENOSPC, EIO when writing to stdout, Akim Demaille, 2012/01/30
- Re: [PATCH] do not ignore errors like ENOSPC, EIO when writing to stdout, Jim Meyering, 2012/01/30
- Re: [PATCH] do not ignore errors like ENOSPC, EIO when writing to stdout, Akim Demaille, 2012/01/31
- Re: [PATCH] do not ignore errors like ENOSPC, EIO when writing to stdout, Jim Meyering, 2012/01/31
Re: [PATCH] do not ignore errors like ENOSPC, EIO when writing to stdout, Akim Demaille, 2012/01/31