On Thu, Mar 27, 2008 at 8:30 PM, Max Battcher <[EMAIL PROTECTED]> wrote: > Gary King wrote: > > On Mar 27, 2008, at 12:16 AM, Max Battcher wrote: > >> Maybe I'll > >> write an article on my impressions of Darcs and Context files versus > >> Tags... > > > > > > I would love to read it! > > > > (more darcs "best practices" articles, etc. would be a big help). > > Here's a first rough draft: > > http://blog.worldmaker.net/2008/mar/27/darcs-and-useful-context-file/ > > -- > --Max Battcher-- >
Useful stuff. Now that I've learned that contexts can be used in this way, this is much cooler. However, what about being able to enter the context file contents at standard input? "darcs failed: option `--context' requires an argument FILENAME" Contexts DEFINITELY deserve much more publicity. Documentation is something that could be worked on, and general usability of the program, but I guess that's because I've come from learned Mercurial through it's documentation. It's so important, though. The reason I asked about revision identifiers is because I'm looking at writing a program that will need to navigate files in a source repository - and people need to be able to specify specific versions of a file to use. So, I'm hoping it's not too much bother, but how does one narrow down the patches (to produce a context file?) that are used to reproduce a file? Am I right to say: in other words what is a command to find all the patches that depend the addfile patch of a particul file? -- Declan Naughton _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
