> This is a proposal for how I think "fossil rm" should work. It's
> consistent with how "svn rm" works.
> At present it's not what happens.
I was refering to the fact that "fossil update" currently does not recreate
a deleted file. It is necessary to do a "fossil revert". There are some people,
On Fri, Dec 11, 2009 at 4:50 AM, wrote:
> Please commit -M/--message-file changes v r waiting...
>
Good morning! i would love to, but DRH asked me to hold off until he reports
back.
Here's the current diff, though, using the names -M and --message file:
step...@jareth:~/cvs/fossil/fossil$
I described this a few days ago, but not very coherently. Here's
another try. I'm happy to bung this in a tracker somewhere if someone
hands me a url.
Problem:
I believe there is a bug with "fossil mv": it lets me move a file
outside of the change controlled tree, at which point ther
Benjohn Barnes wrote:
> I described this a few days ago, but not very coherently. Here's
> another try. I'm happy to bung this in a tracker somewhere if someone
> hands me a url.
http://www.fossil-scm.org/index.html/reportlist
--
Daniel JB Clark | Sys Admin, Free Software Foundation
pobox.
D. Richard Hipp wrote:
> On Dec 2, 2009, at 10:52 AM, Daniel Clark wrote:
>
>> For a while it's seemed odd to me that google hadn't updated its
>> indexes
>> of a few sites, so I took a look and noticed the obvious - robots.txt
>> was disallowing all crawlers:
>>
>> (from main.c)
>>
>> /* Preve
On Dec 11, 2009, at 5:07 AM, Stephan Beal wrote:
> On Fri, Dec 11, 2009 at 4:50 AM, wrote:
> Please commit -M/--message-file changes v r waiting...
>
>
> Good morning! i would love to, but DRH asked me to hold off until he
> reports back.
I'm sorry. I intended for you to hold off until
Stephan Beal wrote:
> On Fri, Dec 11, 2009 at 4:50 AM, wrote:
>
> > Please commit -M/--message-file changes v r waiting...
> >
>
>
> Good morning! i would love to, but DRH asked me to hold off until he reports
> back.
>
I thought he was working on a method of my #1 item, i.e. saving the
=?ISO-8859-1?Q?Ramon_Rib=F3?= wrote:
> > This is a proposal for how I think "fossil rm" should work. It's
> > consistent with how "svn rm" works.
> > At present it's not what happens.
>
>
> I was refering to the fact that "fossil update" currently does not recreate
> a deleted file. It is neces
Benjohn Barnes wrote:
> I described this a few days ago, but not very coherently. Here's
> another try. I'm happy to bung this in a tracker somewhere if someone
> hands me a url.
>
Benjohn,
Maybe file a ticket at: http://www.fossil-scm.org/index.html/tktnew
Jeremy
_
What I meant was the following:
rm file1
fossil update
in others VCS like CVS, file "file1" would appear again on disk. in
fossil it does not.
fossil revert file1
Now, it appears on disk
Compass Ing. y Sistemas Dr. Ramon Ribo
http://www.compassis.com ram...@compassis.com
c/
On Dec 11, 2009, at 6:48 AM, Ramon Ribó wrote:
> What I meant was the following:
>
> rm file1
> fossil update
>
> in others VCS like CVS, file "file1" would appear again on disk. in
> fossil it does not.
>
> fossil revert file1
>
> Now, it appears on disk
Oh, yuck. I could have sworn that I'd tr
In fact, fossil is saying that the merge between a file and a
deleted file is a deleted file. Which is something to what I would
strongly agree.
RR
2009/12/11 Will Duquette :
> On Dec 11, 2009, at 6:48 AM, Ramon Ribó wrote:
>
>> What I meant was the following:
>>
>> rm file1
>> fossil update
On Fri, Dec 11, 2009 at 2:11 PM, Jeremy Cowgar wrote:
> I thought he was working on a method of my #1 item, i.e. saving the commit
> message when a commit had failed. I didn't think he was working on anything
> in regards to #2... loading the commit message from a file.
>
> (I'm also waiting :-D)
On Fri, Dec 11, 2009 at 4:51 PM, Stephan Beal wrote:
> Here it is:
>
>
> http://www.fossil-scm.org/index.html/vinfo/9517cc7486cb68df5de66ae7000337ea2d718574
>
@Richard: can you please double-check the bottom-most part, to ensure that
i've handled the 0-length case properly vis-a-vis the new "ci-
I have various versions of fossil around and I see in the 2009-02-13
20:30 version the Check-in page shows File Changes section where the changed
files are listed and you have to click them to view the diffs and history. In
the 2009-11-23 22:14 version that section is now labeled Change
On Dec 11, 2009, at 10:51 AM, Stephan Beal wrote:
> On Fri, Dec 11, 2009 at 2:11 PM, Jeremy Cowgar
> wrote:
> I thought he was working on a method of my #1 item, i.e. saving the
> commit message when a commit had failed. I didn't think he was
> working on anything in regards to #2... loadi
On Dec 11, 2009, at 10:58 AM, verizon wrote:
> I have various versions of fossil around and I see in the
> 2009-02-13 20:30 version the Check-in page shows File Changes
> section where the changed files are listed and you have to click
> them to view the diffs and history. In the 200
On Fri, Dec 11, 2009 at 4:58 PM, D. Richard Hipp wrote:
> The comment text is no longer preserved if the commit aborts. I
> didn't actually test this, I'm just looking at the code. But it
> appears that the comment text is only preserved if the comment is an
> empty string - not very useful.
Stephan Beal wrote:
> On Fri, Dec 11, 2009 at 2:11 PM, Jeremy Cowgar wrote:
>
> > I thought he was working on a method of my #1 item, i.e. saving the commit
> > message when a commit had failed. I didn't think he was working on anything
> > in regards to #2... loading the commit message from a f
19 matches
Mail list logo
