[Nix-dev] bash updates

[Shea Levy]

Is there any reason we can't just do a full merge? I'd rather try to fix any potentially broken things in updates now than split the current updates into two stdenv-changing merges. 
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Peter Simons <simons at cryp.to> wrote:

Hi guys,

I would like merge the update to Bash version 4.2 into trunk. Right now,
the changes are in 'stdenv-updates', but that branch contains a whole
lot of changes that I don't know anything about, so I'd rather not be
responsible for merging the entire branch. So my suggestion would be
that I merge only a subset of 'stdenv-updates', i.e. trivial changes
like the updates to bash, openssl, etc. I could probably do that over
the course of the next week, so that the merge is ready next weekend,
maybe on Sunday evening or so.

Does anyone have a better solution? Or is anyone aware of any reason why
those updates should not be merged into trunk at that time?

Take care,
Peter

_____________________________________________

nix-dev mailing list
nix-dev at lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20110928/5ac4edb4/attachment.html