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: PATCH: Use __builtin_bswap32/64 for GCC >= 4.2


On 04/11/2012 05:26 PM, Ryan S. Arnold wrote:
On Tue, Apr 10, 2012 at 1:32 PM, Andreas Jaeger<aj@suse.com> wrote:
On 04/06/2012 09:16 PM, Roland McGrath wrote:
[...]

When publishing branches, it's far more useful if you make them ones we
could merge directly.  So include a proper ChangeLog entry in the branch.
We don't want the intermediate history to be merged in.  So instead of
just
pushing an incremental commit onto your branch, rebase and replace the
branch with the new single commit that is ready for merge.  The server's
hooks prevent you from pushing a rebase directly, but you can do:
        git push origin :hjl/bswap # delete the old branch
        git push origin hjl/bswap # re-create under the same name


Roland, could you document the above in the glibc wiki, please?

I can add this to the wiki. It can go in one of the following two pages:


http://sourceware.org/glibc/wiki/GlibcGit
http://sourceware.org/glibc/wiki/Committer%20checklist

I think the GlibcGit page is the proper place and I can add a section
on developing large features in namespace branches.

I've already added a brief section at the end of consensus: http://sourceware.org/glibc/wiki/Consensus

I suggest you enhance it - and consider moving it to another place.

Thanks,
Andreas
--
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 NÃrnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix ImendÃrffer,HRB16746 (AG NÃrnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


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