On 9 Dec 2009, at 21:21, fossil-users-requ...@lists.fossil-scm.org
wrote:
Which is exactly why fossil rm *.foo should delete *.foo from the
file system as well as from the repository. If you forget, and do rm
*.foo, then you can ask fossil to give you the files back, and then
do fossil rm
Hi,
I've managed to get my working copy in to a funny state. I performed a
fossil mv on a file, and gave a destination outside of the checkin
tree. Fossil was happy to perform this operation, but now I'm not able
to correct the mistake. If I try to move the file back in, I get the
error
I don't care what the long name for the option is but I do think -M is
a mistake. off the top of my head I can't think of any fossil
parameters that are not lowercase but perhaps there is. can someone
confirm that the fossil command line parameters are even case sensitive?
I agree that
I offered a (horrible) work around. Fortunately, I thought better of
it for my particular case, where my working set was in the middle of a
merge.
Instead, I've used sqlite on the command line to find a row in the
vfile table and correct it's pathname so it's where I meant to move
it to,
My 2 cents. --keep and --force options are intuitive, I would prefer them.
- Altu
-Original Message-
From: Joshua Paine jos...@letterblock.com
To: fossil-users@lists.fossil-scm.org
Sent: Thu, Dec 10, 2009 3:15 am
Subject: Re: [fossil-users] 3 Feature requests - globbing using the
Wilson, Ronald wrote:
One of the thinks that I most dislike of other VCS is the excess of
options. Too many options means to much time reading the manuals and
to much time remembering the possibilities of the tool.
Fossil is very good at it. It has the minimum set of options to make the
Stephan Beal sgb...@googlemail.com wrote:
i'm with Jeremy on this one: -M/--message-file. That said, Richard's been
interestingly quiet throughout this conversation, which leads me to suspect
that he's hacking away at some clever alternative which will make all this
moot :).
SVN uses -F
Ramon Ribó wrote:
that -M filename is also a useful choice. Regarding the bloat factor: the
diff for -M is only a few lines of real code. i've pasted it below, but
In my opinion, the decision should not be based on the added
complexity to the code (we programmers can deal with complexity,
IMHO it would be nice to have and RSS link on the page text.
I'd also really love if each page could also have its own RSS feed.
This way people could subscribe and be notified of changes only to pages
they are interested in, instead of all changes which can be overwhelming.
This would be esp.
I was unclear, apparently.
Suppose fossil rm *.foo deletes the files from the file system and
from Fossil.
If I then do
rm *.foo
when I meant to do
fossil rm *.foo
I can then do
fossil update
which will give me my *.foo files back. Then, I can do
fossil rm *.foo
Note
Will Duquette w...@wjduquette.com wrote:
I was unclear, apparently.
Suppose fossil rm *.foo deletes the files from the file system and
from Fossil.
If I then do
rm *.foo
when I meant to do
fossil rm *.foo
I can then do
fossil update
which will give me my
On Dec 10, 2009, at 6:39 AM, Jeremy Cowgar wrote:
Will Duquette w...@wjduquette.com wrote:
I was unclear, apparently.
Suppose fossil rm *.foo deletes the files from the file system and
from Fossil.
If I then do
rm *.foo
when I meant to do
fossil rm *.foo
I can then do
On Thu, Dec 10, 2009 at 06:25:57AM -0500, D. Richard Hipp wrote:
On Dec 9, 2009, at 11:26 PM, Michael wrote:
Synopsis:
I am trying to use a CGI/1.1 webserver to serve fossil repositories.
The pages do not display properly. Via 'view source' from the
browser, I see the extra word
If I then do
rm *.foo
when I meant to do
fossil rm *.foo
I can then do
fossil update
which will give me my *.foo files back.
Are you sure that this command is going to give that files back? Have
you tried it?
This is another field where there are currently proposals to
=?ISO-8859-1?Q?Ramon_Rib=F3?= ram...@compassis.com wrote:
If there is an option that a user has no interest in using, why would
the user attempt to remember what it was?
I recently had to read the cvs manual to find an option of one
subcommand. I assure you that it was not a pleasant task
Hm, I just browsed the man pages of many VCS systems (CVS included) to find
examples of parameters for the message file. I had no problem locating their
pages, browsing the manual and finding them for 6 VCS systems in about 3
minutes.
You must be cleverer than me ... or I felt my 3
On Dec 9, 2009, at 4:45 PM, Joshua Paine wrote:
On Wed, 2009-12-09 at 22:22 +0100, Stephan Beal wrote:
That said, presumably when you rm a file, it already exists in the
repo, and the chance of a significant loss due to an unwanted unlink()
on the file seems to be small.
[...]
Re:
Stephan Beal sgb...@googlemail.com wrote:
i've just added -M/--comment-file which does #2. If there are no objections
to using -M/--comment-file for this, i will commit it.
Where are we at with this? I've been looking forward to seeing a commit message
:-D
Jeremy
On Dec 10, 2009, at 7:30 AM, Ramon Ribó wrote:
If I then do
rm *.foo
when I meant to do
fossil rm *.foo
I can then do
fossil update
which will give me my *.foo files back.
Are you sure that this command is going to give that files back? Have
you tried it?
This is
19 matches
Mail list logo
