On Tue, 15 Jan 2008, Ralf S. Engelschall wrote:
Sorry, in case this seems too strange for most of you, but it a
"problem" I'm faced with mostly every day and I really would appreciate
some additional support from Monotone. Let me describe...
While I'm in "wild hacking mode" I adjust many source
Derek Scherger wrote:
The idea I had in mind would be something like, commit the current
revision to your local db *without* a branch cert, but perhaps with some
other paused cert that gives a name to each paused revision. This commit
would be done by the pause command. After committing the pau
[ William, for double post Why this list doesn't set Reply-to header ? ]
2008/1/16, William Uther <[EMAIL PROTECTED]>:
> I like this 'commitdiff' concept. It is a simple command that could be
+1 for commitdiff from here. It's very good idea.
> The only real question is how this affect items tha
> "Alvaro" == Alvaro Herrera <[EMAIL PROTECTED]> writes:
Alvaro> Yeah, what I do is save the full diff somewhere, get the partial
diff
Alvaro> with filterdiff, save it to a tmp file, revert all changes, apply
the
Alvaro> partial diff, commit, apply the full diff back. Lather, ri
Thomas Keller wrote:
So, what could one do instead? Maybe it would be a good idea to record
different patch sets somehow differently:
$ vi some_file.cpp
$ mtn stack some_file.cpp
$ vi some_file.cpp
$ vi other_file.cpp
$ mtn stack some_file.cpp other_file.cpp
$ mtn ls stacks
1: changed some_file.
On 16/01/2008, at 3:02 AM, Alvaro Herrera wrote:
Ralf S. Engelschall wrote:
On Tue, Jan 15, 2008, Thomas Moschny wrote:
On Tuesday 15 January 2008, Ralf S. Engelschall wrote:
So, it would be also nice
to have the "hunk restriction" feature for "mtn diff":
$ mtn diff file11:-2,-4
You
Alvaro Herrera wrote:
> Yeah, what I do is save the full diff somewhere, get the partial diff
> with filterdiff, save it to a tmp file, revert all changes, apply the
> partial diff, commit, apply the full diff back. Lather, rinse, repeat.
> It's truly cumbersome.
Notwithstanding the question whet
Ralf S. Engelschall wrote:
> On Tue, Jan 15, 2008, Thomas Moschny wrote:
>
> > On Tuesday 15 January 2008, Ralf S. Engelschall wrote:
> > > So, it would be also nice
> > > to have the "hunk restriction" feature for "mtn diff":
> > >
> > > $ mtn diff file11:-2,-4
> >
> > You can use filterdiff
On Tue, Jan 15, 2008, Thomas Moschny wrote:
> On Tuesday 15 January 2008, Ralf S. Engelschall wrote:
> > So, it would be also nice
> > to have the "hunk restriction" feature for "mtn diff":
> >
> > $ mtn diff file11:-2,-4
>
> You can use filterdiff from the very useful patchutils[1] collection
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf S. Engelschall schrieb:
> $ mtn ci -m "description of logical change1" file11:-2,-4 ... file1N
> $ mtn ci -m "description of logical change2" file21:+2,+4 ... file2N
> $ mtn ci -m "description of logical change3" file31 ... file3
On Tuesday 15 January 2008, Ralf S. Engelschall wrote:
> So, it would be also nice
> to have the "hunk restriction" feature for "mtn diff":
>
> $ mtn diff file11:-2,-4
You can use filterdiff from the very useful patchutils[1] collection for that:
mtn diff file11 | filterdiff -# 1,3,5-
woul
Sorry, in case this seems too strange for most of you, but it a
"problem" I'm faced with mostly every day and I really would appreciate
some additional support from Monotone. Let me describe...
While I'm in "wild hacking mode" I adjust many source files. Once
everthing works I have to decide on ho
12 matches
Mail list logo
