On Thu, February 9, 2012 7:47 am, Konstantin Khomoutov wrote:
On Thu, Feb 09, 2012 at 01:55:01AM +0100, frantisek holop wrote:
fossil always reports the latest artifact ID and commit message
whenever doing 'fossil up', even though actually there was no new
check-in.
for example:
$ fossil
hmm, on Thu, Feb 09, 2012 at 08:19:36AM -, Eric said that
fossil update is concerned only with the branch you have in your checkout
directory. If autosync is on it does a pull first, but that's a separate
operation, and it os concerned only with artifacts in the repository and
knows
Le 2012-02-09 à 05:04, frantisek holop min...@obiit.org a écrit :
hmm, on Thu, Feb 09, 2012 at 08:19:36AM -, Eric said that
fossil update is concerned only with the branch you have in your checkout
directory. If autosync is on it does a pull first, but that's a separate
operation, and it
hmm, on Thu, Feb 09, 2012 at 05:58:47AM -0500, Martin Gagnon said that
i have never used git. i would simply prefer fossil to report nothing
if there is nothing to report...
$ fossil up
$
come to think of it, as a developer i am not really interested in
fossil's traffic
On Thu, 9 Feb 2012 08:19:36 -
Eric e...@deptj.eu wrote:
[...]
$ fossil up
Autosync: http://www.fossil-scm.org/
Bytes Cards Artifacts Deltas
Sent: 177 2 0 0
Received:2608 57 0 0
On Feb 8, 2012, at 17:05 , Richard Hipp wrote:
I generally don't stress over a 10MB file on my 1TB disk drive, though...
Still, it probably would not hurt to have Fossil do vacuum from time to time,
would it?
Kind regards,
Remigiusz Modrzejewski
On Feb 7, 2012, at 23:11 , Stephan Beal wrote:
Agreed completely - spaces in filenames are evil. (let the flame wars begin
;)
Well, shouldn't a good filename start with - anyways? ;)
Kind regards,
Remigiusz Modrzejewski
___
fossil-users
On Thu, Feb 9, 2012 at 6:08 PM, Remigiusz Modrzejewski
l...@maxnet.org.plwrote:
Well, shouldn't a good filename start with - anyways? ;)
i once administered a Solaris system where someone accidentally managed,
over a serial terminal, to touch a new file whos name was a single
backspace
On Fri, Feb 10, 2012 at 02:26, Stephan Beal sgb...@googlemail.com wrote:
i once administered a Solaris system where someone accidentally managed,
over a serial terminal, to touch a new file whos name was a single
backspace character (ASCII 0x08). The only way we managed to delete it was
hmm, on Fri, Feb 10, 2012 at 03:12:01AM +0900, MIURA Masahiro said that
On Fri, Feb 10, 2012 at 02:26, Stephan Beal sgb...@googlemail.com wrote:
i once administered a Solaris system where someone accidentally managed,
over a serial terminal, to touch a new file whos name was a single
On Thu, 9 Feb 2012 17:02:19 +0400, Konstantin Khomoutov
flatw...@users.sourceforge.net wrote:
On Thu, 9 Feb 2012 08:19:36 -
Eric e...@deptj.eu wrote:
snip
fossil update is concerned only with the branch you have in your
checkout directory. If autosync is on it does a pull first, but
Hi List,
I ran into a strange problem which results in fossil commit failure
after a specific type of merge.
I attached a self-contained shell script that reproduces the problem.
Tested with trunk version of fossil on Linux.
Here is the problem description.
A fossil repository T.fossil contains
+1
I faced this a couple of days back and had to perform an incorrect commit.
- Original Message -
From: Leo Razoumov
Sent: 02/10/12 03:39 AM
To: Fossil SCM user's discussion
Subject: [fossil-users] fossil commit failure after merge
Hi List,
I ran into a strange problem which
On Thu, Feb 9, 2012 at 23:27, altufa...@mail.com wrote:
+1
I faced this a couple of days back and had to perform an incorrect commit.
Thanks for confirming my observations. I think this is a serious
issue. I try to follow a policy of never committing to a public branch
code that does not
14 matches
Mail list logo
