Thanks for this, Gracjan, On 11 September 2012 07:38, Gracjan Polak <[email protected]> wrote:
> There was source code and a build script. I wanted to push changes to > source code but keep my build script changes local for just a little while. > 'darcs push' asked me about my changes to source [1/2], there I said 'Y'. > Then it did not ask any more question, just pushed the build script patch > upstream too. > Apologies if I'm asking you to repeat for failing to read properly. Do I understand correctly that - you were offered two patches S and B - patch S was your source code change - patch B was your build script change - that patch S was offered before B - when you accepted S, B was automatically accepted as well without giving you recourse? If so, that is not normal. The behaviour I would expect is - it offers B first - if you reject B, it does not offer S I'm trying to think of possible ways the behaviour I think you reported could arise. By any chance were you using the --reverse flag? Are you still using Darcs enough that you can dig up an example? Thanks, -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
