2011-05-30, 06:34(+00), Michael Witten:
[...]
> Ben, it is generally a good idea to maintain the `Cc' list unless
> explicitly asked.
Beware that the bash mailing list also has a usenet interface
(gnu.bash.bug) which has no notion of recipients let alone Cc.
--
Stephane
On Fri, Jun 3, 2011 at 15:27, Bradley M. Kuhn wrote:
> Sorry, I was imprecise in my wording in my email yesterday. By "use
> separate branches for individual developers", I meant that "branches
> would be created for those developers who wanted to develop publicly in
> a Git repository".
Such de
Chet Ramey wrote at 15:59 (EDT) on Thursday:
> I think there should be a master branch, and a branch that includes
> posted patches other than those that have been "officially released."
> Then other branches as needed to accommodate developers.
I think that could work fine; I'm happy to do my be
On 6/2/11 1:00 PM, Bradley M. Kuhn wrote:
> Chet Ramey wrote at 17:25 (EDT) on Wednesday:
>> I think this is a great idea. I've already contacted Bradley and
>> encouraged him to go ahead. I'd like to thank him publicly for his
>> offer.
>
> Thanks, Chet! It was my pleasure to set this up. Tha
>On Thu, Jun 2, 2011 at 17:00, Bradley M. Kuhn wrote:
>> I'd suggest that we keep the master branch only to track the history of
>> releases and officially released patches as Chet posts them, and then we
>> can use separate branches for individual developers who want to use Git.
>> What do you th
On Thu, Jun 2, 2011 at 17:00, Bradley M. Kuhn wrote:
> I'd suggest that we keep the master branch only to track the history of
> releases and officially released patches as Chet posts them, and then we
> can use separate branches for individual developers who want to use Git.
> What do you think o
Chet Ramey wrote at 17:25 (EDT) on Wednesday:
> I think this is a great idea. I've already contacted Bradley and
> encouraged him to go ahead. I'd like to thank him publicly for his
> offer.
Thanks, Chet! It was my pleasure to set this up. Thanks to Jari for
the original idea and the first att
On 5/29/11 10:18 PM, Bradley M. Kuhn wrote:
> I did some research this weekend and collected all the old versions of Bash
> I could find. I've carefully organized all this into a repository,
> making the commits as find-grained as possible given what's available in
> the permanent public record.
Bradley M. Kuhn wrote:
I humbly suggest that http://git.savannah.gnu.org/cgit/bash.git be
replaced with this repository above that I've created. The new
repository contains everything that the current Savannah one does, but I
put much more effort into making commits fine-grained, rather than
me
Michael Witten wrote at 02:34 (EDT):
> Perhaps (and hopefully) Bradley meant that file moves were separated
> from any other content changes that might otherwise have occurred
> simultaneously.
I probably did this in some cases and not others. Anyway, what I've got
is clearly better than what's
On Mon, May 30, 2011 at 05:06, Ben Pfaff wrote:
> "Bradley M. Kuhn" writes:
>
>> The new repository contains everything that the current
>> Savannah one does, but I put much more effort into making
>> commits fine-grained, rather than merely importing the public
>> releases blindly. (For example
"Bradley M. Kuhn" writes:
> The new repository contains everything that the current
> Savannah one does, but I put much more effort into making
> commits fine-grained, rather than merely importing the public
> releases blindly. (For example, I did 'git mv' where it was
> obvious a move occurred,
On Mon, May 30, 2011 at 03:09, Bradley M. Kuhn wrote:
>
> Michael Witten replied a few minutes ago:
>> it is my opinion that all further development should take place through
>> a public, distributed repository such as the one you have created -
>> regardless of Chet's objections.
>
> It seems tha
I wrote earlier this evening:
> > I humbly suggest that http://git.savannah.gnu.org/cgit/bash.git be
> > replaced with this repository above that I've created. The new
> > repository contains everything that the current Savannah one does, but I
> > put much more effort into making commits fine-gra
On Mon, May 30, 2011 at 02:18, Bradley M. Kuhn wrote:
> Chet Ramey wrote on 2009-11-02:
>> Jari Aalto was setting up a git repository of current and older bash
>> versions on savannah. I'll keep him up to date with public versions
>> of bash
>
> Bob Proulx wrote on 2009-11-02:
>>> It looks like i
On Sunday, May 29, 2011 22:18:33 Bradley M. Kuhn wrote:
> It's been two years since this discussion began
and there have been requests older than that. you just found the most
"recent".
-mike
signature.asc
Description: This is a digitally signed message part.
Chet Ramey wrote on 2009-11-02:
> Jari Aalto was setting up a git repository of current and older bash
> versions on savannah. I'll keep him up to date with public versions
> of bash
Bob Proulx wrote on 2009-11-02:
>> It looks like it has just recently been partially implemented.
>> http://git.
Bob Proulx wrote:
> Jan Schampera wrote:
>> The official patches should be there as individual commits. Though, I
>> admit it's not a small amount of work to do all that for the past
>> releases. Such a GIT or SVN repository technically is easy to do, but
>> who feeds it :(
>
> Moving forward from
Jan Schampera wrote:
> The official patches should be there as individual commits. Though, I
> admit it's not a small amount of work to do all that for the past
> releases. Such a GIT or SVN repository technically is easy to do, but
> who feeds it :(
Moving forward from now it should be reasonably
Chet Ramey schrieb:
> That's how I prefer it. I don't do public development on savannah, and
> I do controlled test releases.
The official patches should be there as individual commits. Though, I
admit it's not a small amount of work to do all that for the past
releases. Such a GIT or SVN reposi
André Goddard Rosa wrote:
> On Mon, Nov 2, 2009 at 10:40 PM, Bob Proulx wrote:
>> Chet Ramey wrote:
>>> Jari Aalto was setting up a git repository of current and older bash
>>> versions on savannah. I'll keep him up to date with public versions
>>> of bash (including, probably, public betas).
>>
On Mon, Nov 2, 2009 at 10:40 PM, Bob Proulx wrote:
> Chet Ramey wrote:
>> Jari Aalto was setting up a git repository of current and older bash
>> versions on savannah. I'll keep him up to date with public versions
>> of bash (including, probably, public betas).
>
> It looks like it has just recen
Chet Ramey wrote:
> Jari Aalto was setting up a git repository of current and older bash
> versions on savannah. I'll keep him up to date with public versions
> of bash (including, probably, public betas).
It looks like it has just recently been partially implemented.
http://git.savannah.gnu.o
Mike Frysinger wrote:
> On Monday 02 November 2009 16:10:40 Chet Ramey wrote:
>>> Is there a public source repository for bash? I could not find
>>> this information in the main homepage.
>> There is no public source repository.
>
> any idea when that'll change ? i asked some time ago (years
On Monday 02 November 2009 16:10:40 Chet Ramey wrote:
> > Is there a public source repository for bash? I could not find
> > this information in the main homepage.
>
> There is no public source repository.
any idea when that'll change ? i asked some time ago (years?) and was said
that it w
> Is there a public source repository for bash? I could not find
> this information in the main homepage.
There is no public source repository.
> I'd like to provide a patch for it.
You can send it to bug-b...@gnu.org. If you could use bashbug, that would
be better. Thanks.
Chet
--
26 matches
Mail list logo
