[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nano-devel] polished git repo
From: |
Benno Schulenberg |
Subject: |
Re: [Nano-devel] polished git repo |
Date: |
Tue, 08 Mar 2016 21:21:21 +0100 |
On Tue, Mar 8, 2016, at 19:30, Chris Allegretta wrote:
> I think it makes sense to do what was previously discussed, put the
> gnulib changes into 2.5 and then once we have all the features we're
> going to need for awhile, brand that 2.6.
Hmm... okay.
> I thought Mike already had access to
> the repo; just made it so he does.
Cool.
Mike, you can put in the gnulib patches whenever you like.
During ./autogen.sh I see the following:
Updating file m4/codeset.m4 (backup in m4/codeset.m4~)
Updating file m4/glibc21.m4 (backup in m4/glibc21.m4~)
Updating file m4/inttypes_h.m4 (backup in m4/inttypes_h.m4~)
Updating file m4/lib-ld.m4 (backup in m4/lib-ld.m4~)
Updating file m4/lib-link.m4 (backup in m4/lib-link.m4~)
Updating file m4/lib-prefix.m4 (backup in m4/lib-prefix.m4~)
Updating file m4/stdint_h.m4 (backup in m4/stdint_h.m4~)
Those files can probably be deleted by your patches?
Benno
--
http://www.fastmail.com - Or how I learned to stop worrying and
love email again
- Re: [Nano-devel] polished git repo, Benno Schulenberg, 2016/03/06
- Re: [Nano-devel] polished git repo, Chris Allegretta, 2016/03/07
- Re: [Nano-devel] polished git repo, Benno Schulenberg, 2016/03/07
- Re: [Nano-devel] polished git repo, Chris Allegretta, 2016/03/08
- Re: [Nano-devel] polished git repo,
Benno Schulenberg <=
- Re: [Nano-devel] polished git repo, Mike Frysinger, 2016/03/08
- Re: [Nano-devel] polished git repo, Jordi Mallach, 2016/03/09
- Re: [Nano-devel] polished git repo, Benno Schulenberg, 2016/03/09
- Re: [Nano-devel] polished git repo, Chris Allegretta, 2016/03/10
- Re: [Nano-devel] polished git repo, Chris Allegretta, 2016/03/29
- Re: [Nano-devel] polished git repo, Mike Frysinger, 2016/03/29
- Re: [Nano-devel] polished git repo, Jordi Mallach, 2016/03/30