From: Albert ARIBAUD <albert.aribaud@3adev.fr>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: Y2038 work branch in the official GLIBC git repo?
Date: Fri, 21 Oct 2016 13:55:00 -0000 [thread overview]
Message-ID: <20161021155511.316735c5.albert.aribaud@3adev.fr> (raw)
In-Reply-To: <ab2bf466-9557-f6f5-88f0-de66018f8d17@linaro.org>
Hi Adhemerval,
On Thu, 20 Oct 2016 13:12:21 -0200, Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote :
> On 18/10/2016 18:27, Albert ARIBAUD wrote:
> > Hi,
> >
> > I would like to make experimental work for Y2038 GLIBC available for
> > others to see, try and comment.
> >
> > I see there are lots of branches already in the official repo at
> > git://sourceware.org/git/glibc.git.
> >
> > Would it be possible to create one for y2038 work? Apparently, many of
> > the existing branches are of the form 'nickname/topic' or even
> > 'nickname/topic/subtopic'; It would be perfect if I could follow the
> > same convention, and create branches like 'aaribaud/y2038[/whatever]'.
> >
> > Is this possible? If so, how should I proceed?
>
> I think as long you have write access you are free to create branches
> inside your name (nickname/...). I would just recommend you to clean
> up regularly old non active branches. For other namespace branch you
> will need to check out this [1].
>
> You can get write access by following the steps described at 'Becoming
> a maintainer (developer)' [2].
>
> [1] https://sourceware.org/glibc/wiki/GlibcGit#Name_Space_Request
> [2] https://sourceware.org/glibc/wiki/MAINTAINERS
Thanks a lot!
Cordialement,
Albert ARIBAUD
3ADEV
prev parent reply other threads:[~2016-10-21 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 20:27 Albert ARIBAUD
2016-10-20 15:12 ` Adhemerval Zanella
2016-10-21 13:55 ` Albert ARIBAUD [this message]
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=20161021155511.316735c5.albert.aribaud@3adev.fr \
--to=albert.aribaud@3adev.fr \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).