Is it possible to actually select patches using hash as a criteria? e.g.
$ darcs pull --hash=c4562f16369940396bc3c97c207ab19978996e5e
What about using date as a criteria? e.g.
$ darcs pull --date=20050822135224
$ darcs unrecord --date=20050822 # all patches on 22-08-2005
Of course this opens a whole can of worms:
+ ranges
$ # all patches from Aug 01 thru Sep 15
$ darcs unpull --date=200508..20050915
This is something that I think svn gets mostly right, just
because it provides so much flexibility.[1]
+ boolean operations (modeled after find cli)
# all patches names stuff or things and dated Dec 21 thru 23.
$ darcs pull \( --patches=/stuff/ -o --patches=/things/ \) -a --
date=20051221..23
I'm still a darcs noob, but I'm currently using it mostly for static
html work and I am feeling like there is some lack of expressiveness
in sorting through lots of small patches. Especially since the
patches don't necessarily correspond to a specifically namable
functionality or bug.
Corey
1. http://svnbook.red-bean.com/en/1.1/ch03s03.html#svn-ch-3-sect-3.3
On Dec 22, 2005, at 4:49 AM, Albert Reiner wrote:
Just a few comments:
[Jason Dagit <[EMAIL PROTECTED]>, Wed, 21 Dec 2005
22:59:47 -0800]:
1. Conflicts should be handled more like recording. You know who the
conflict came from, you get a chance to deal with it or ignore it, it
can be interactive, and maybe copies should be made (a copy of each
version and the copy with war paint). As a sub point, I'm not
convinced that when using a "central darcs repo" that all conflicts
can be resolved without working in the central repo.
My feeling is that this interactive scheme only works for simple
situations, e.g., those where you only have to choose between two
alternatives. At any rate, by making the central repo accept a patch
only if it applies cleanly and a test suite runs, it seems clear that
you can set up a situation where nothing is to be done in the central
repo but only in copies of it.
2. Integration with more software. Here is an incomplete list of
software I've wanted darcs plugins for:
But this does not seem to concern darcs proper but should be separate
projects, I think.
6. A way to get automatic "unique" names for patches that you DO NOT
have to think about.
I think you already have them, just that they are not displayed by
default. E.g., in one repo I have 119 patches called '[] [nw]'. But
I can easily get the unique name with --xml output:
$ darcs cha --pat '^\[\] \[nw\]$' | wc -l
119
$ darcs cha --pat '^\[\] \[nw\]$' --xml | tail
<patch author='Albert Reiner <[EMAIL PROTECTED]>'
date='20050822135224' local_date='Mon Aug 22 15:52:24 CEST 2005'
inverted='False' hash='20050822135224-50f25-
c4562f16369940396bc3c97c207ab19978996e5e.gz'>
<name>[] [nw]</name>
</patch>
<patch author='Albert Reiner <[EMAIL PROTECTED]>'
date='20050822135346' local_date='Mon Aug 22 15:53:46 CEST 2005'
inverted='False' hash='20050822135346-50f25-
de901a7c5bcbe85b9aceb6eb3096b073cb97d936.gz'>
<name>[] [nw]</name>
</patch>
<patch author='Albert Reiner <[EMAIL PROTECTED]>'
date='20050929143643' local_date='Thu Sep 29 16:36:43 CEST 2005'
inverted='False'
hash='20050929143643-50f25-828dfeda1ed2179950fcfeede721d4ab01c377d6.gz
'>
<name>[] [nw]</name>
</patch>
</changelog>
Regards,
Albert.
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
Corey Jewett
[EMAIL PROTECTED]
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
