2012/9/10 Owen Stephens <[email protected]> > On 10 September 2012 15:49, Gracjan Polak <[email protected]> wrote: > >> Silent pushing of dependent patches when the reason of dependency is not >> clear was my main issue with darcs. >> >> 1. darcs push >> 2. select patches I want to push >> 3. discover that something else to my understanding unrelated got >> pushed too (darcs was thinking differently) >> 4. work hard to fix upstream repo >> >> >> I can't recall Darcs ever "silently" pushing patches it didn't ask me > about. >
It decided that some other patches were dependencies of one I wanted to push. > What do you mean by unrelated? Unless there's a textual overlap, distinct > changes > should not arbitrarily depend on each other. > 'Should not' is a keyword here. Darcs did not agree with me and I failed to understand reasons of dependency. I'm not sure if/how textual overlap was there. Also I'm talking darcs 2.4 here, so all of this might be out of date. > > Can you remember what the situation was? > 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. The dependency was probably there, but: - it wasn't obvious why to patches were dependent - I could not react before damage was done > Cheers, > Owen. >
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
