[Default] On Mon, 17 Aug 2015 22:12:11 -0400,
sky5w...@gmail.com wrote:
Nice.
Is it possible to trim the results to only a specific file using a raw SQL
query or TH1?
It probably is possible, start looking at
http://fossil-scm.org/index.html/artifact/aa78af37cb3226cc?ln=717-733
and then
On Mon, Aug 17, 2015 at 1:07 PM, Graeme Pietersz gra...@pietersz.net
wrote:
All the files concerned have a distinctive filename pattern (all start
the same) and would only ever have been in one of two directories in any
version. Not sure if that helps.
Fossil does not shun by filename, but
Nice.
Is it possible to trim the results to only a specific file using a raw SQL
query or TH1?
Or is it quicker to just parse fossil test-whatis-all artifacts.txt
output?
Can I enter multiple artifacts(comma or space delimited) in the shun ui or
only 1 at a time?
Thanks
On Mon, Aug 17, 2015 at
On Mon, 17 Aug 2015 16:37:41 +0530, Graeme Pietersz
gra...@pietersz.net wrote:
I have a Fossil repo that I expected to only work on myself. I have
files containing confidential information and I now need to allow
someone else developer access (so clone, push and pull as a minimum) to
the
On 17/08/15 16:47, Stephan Beal wrote:
Fossil does not shun by filename, but my hash value, so you'll need to
find all hashes of all versions of those files and shun those.
I counted 71 versions of the most frequently changed of those files
a lot easier to recreate.
It is likely far
2014-08-31 5:15 GMT+02:00 Andy Goth andrew.m.g...@gmail.com:
Going to rebuild and keep trying
Also I should mention that the assert failure goes away following rebuild.
Suspecting that you shunned an artifact which was
a trunk commit still referenced from other places.
It's indeed not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm continuing to experiment with putting old versions into the
repository. This necessarily meant numerous false starts and failures
(it's a fool's errand, really), which in turn mean shunning and trying
again (compounding the mistake).
I was able
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/30/2014 10:13 PM, Andy Goth wrote:
$ f up version-4.31 fossil: ./src/bag.c:146: bag_find: Assertion
`e0' failed. Aborted
Going to rebuild and keep trying
Also I should mention that the assert failure goes away following rebuild.
- --
Andy
Hello,
if I shun any contents from a repository, and rebuild... can I later 'unshun'
them, and then expect a 'pull' to get them from whatever repository containing
them?
Regards,
Lluís
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
2011/10/5 Lluís Batlle i Rossell virik...@gmail.com
Hello,
if I shun any contents from a repository, and rebuild... can I later
'unshun'
them, and then expect a 'pull' to get them from whatever repository
containing
them?
I can't think of a reason why that wouldn't work.
--
D. Richard
...@lists.fossil-scm.org [mailto:fossil-users-
boun...@lists.fossil-scm.org] On Behalf Of D. Richard Hipp
Sent: Thursday, October 15, 2009 6:39 PM
To: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] shunning
On Oct 15, 2009, at 5:24 PM, Wilson, Ronald wrote:
I don't
I accidentally added a file to my repository using all lower-case
letters, which basically added a blank artifact to my repository. Later
I added the file again using the proper case. I can't figure out how to
remove the first file. I tried fossil rm but the file still shows on
the file list on
On Oct 15, 2009, at 2:07 PM, Wilson, Ronald wrote:
I accidentally added a file to my repository using all lower-case
letters, which basically added a blank artifact to my repository.
Later I added the file again using the proper case. I can’t figure
out how to remove the first file.
On Oct 15, 2009, at 5:24 PM, Wilson, Ronald wrote:
I don't understand. You said you did:
fossil add file1.txt
fossil add FILE1.txt
fossil commit
And that worked even though file1.txt did not exist? You should
have gotten an error. But even if it did work,
Ok I
14 matches
Mail list logo
