This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Translations gone out for 2.16.


On 6/26/2012 5:19 AM, Thomas Schwinge wrote:
> Hi Carlos!
> 
> On Mon, 25 Jun 2012 21:41:12 -0400, "Carlos O'Donell" <carlos@systemhalted.org> wrote:
>> I've checked in the libc.pot changes for trunk.
>>
>> I have tagged trunk with tag "glibc-2.16-tps" and uploaded a snapshot
>> of the tag for the translation team.
> 
> What's the rationale for the tag?  I'd prefer to keep the number of
> publically visible tags to a bare minimum, that is, the release tags plus
> perhaps exceptional ones such as the ports merge and similar (but I'm not
> even sure we really need these).  In fact, before reading your email I'm
> replying to, I had issued a Âgit fetch sourceware and wondered what that
> new Âglibc-2.16-tps tag was that had been pulled off of sourceware.

The tag will represents a marker for the commit at which the translations
are accurate. The tag was used in conjunction with `make dist' to produce
a snapshot tarball for the translation team. It seemed sensible to me to
create a tag for this particular usage.

(1) Tag message not sufficiently verbose?

The tag itself is an annotated tag with a message explaining the purpose
of the tag, see:

git tag -v glibc-2.16-tps
object 4d0ee855457e9c51854ed384a59457751563e5ac
type commit
tag glibc-2.16-tps
tagger Carlos O'Donell <carlos@systemhalted.org> 1340579376 -0400

Translation project snapshot for 2.16
...

(2) Pros and cons of lots of tags?

Can you talk a little bit more about the pros and cons of limiting
our tagging?

I would like to allow *anyone* to push tags, and use them for whatever
novel purposes they have.

(3) Create a tag namespace?

However, it seems that we may need to develop a tag hierarchy like
we have with the branch namespaces.

Comments?

Cheers,
Carlos.
-- 
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]