Hi List
I'm trying to move my dhcpcd git repository [1] to fossil [2].
While it works for the most part, it seems that the branches called
trunk and dhcpcd-5 have the same commits, which is just wrong.
I have successfully done a git export | git import to a new repository
[3] to see if it's a
On 21/12/2013 21:11, Roy Marples wrote:
I'm trying to move my dhcpcd git repository [1] to fossil [2].
While it works for the most part, it seems that the branches called
trunk and dhcpcd-5 have the same commits, which is just wrong.
By adding a commit to the dhcpcd-5 branch in git, exporting
On 22/12/2013 0:55, Roy Marples wrote:
On 21/12/2013 21:11, Roy Marples wrote:
I'm trying to move my dhcpcd git repository [1] to fossil [2].
While it works for the most part, it seems that the branches called
trunk and dhcpcd-5 have the same commits, which is just wrong.
By adding a commit
Hi List
Can fossil create an archive (tarball, zip file, etc) from a given
artifact id WITHOUT using the web interface?
Something like this is what I need:
$ fossil archive ?ID | bzip2 distribution-version.tar.bz2
Thanks
Roy
___
fossil-users
On 03/01/2014 16:41, Lluís Batlle i Rossell wrote:
On Fri, Jan 03, 2014 at 04:36:26PM +, Roy Marples wrote:
Hi List
Can fossil create an archive (tarball, zip file, etc) from a given
artifact id WITHOUT using the web interface?
Something like this is what I need:
$ fossil archive ?ID
On 03/01/2014 16:42, Richard Hipp wrote:
On Fri, Jan 3, 2014 at 11:36 AM, Roy Marples r...@marples.name wrote:
Hi List
Can fossil create an archive (tarball, zip file, etc) from a given
artifact id WITHOUT using the web interface?
Something like this is what I need:
$ fossil archive ?ID
Hi
On 13/02/2014 15:24, Baptiste Daroussin wrote:
In particular to interact with the submitter. I have found no way to:
1/ send a mail when new ticket is created (yes we can follow via rss
feed, but a mail is way nicer)
I don't have a huge problem with RSS as it looks to be possible to
On 18/02/2014 14:40, Roy Marples wrote:
I don't have a huge problem with RSS as it looks to be possible to
subscribe to all ticket changes which is great for me as a repo admin.
It's also possible subscribe to an individual ticket RSS.
However, using the default skin I don't see an easy way
On 20/02/2014 15:07, Ron Wilson wrote:
On Thu, Feb 20, 2014 at 6:56 AM, Roy Marples r...@marples.name wrote:
Here is a patch which adds a RSS feed icon after the ticket uuid.
Probably not the best way of doing it, but I couldn't think of
another way which would allow the user to use
On 10/03/2014 22:24, Richard Hipp wrote:
The diff-generator in Fossil is unable to cope with lines longer than
8192 bytes.
That could be changed. (It's a #define, though there are adverse
consequences for making it too large.) But is a diff on a file with
huge lines like that really useful?
On 17/03/2014 16:22, ma...@include-once.org wrote:
It's nowhere near finished, but here's a github-simulating layout:
http://fossil.include-once.org/hybrid7/
Barely holds together, and it's not yet working in Firefox. But
includes
fx_search support, my th1x functions for the language bar
On Saturday 27 Sep 2014 11:09:44 Andy Bradford wrote:
Thus said Stephan Beal on Sat, 27 Sep 2014 10:02:50 +0200:
font-family: monospace;
still trying to decide if that is more readable, though. Not yet
convinced.
I tried it and I didn't think it improved anything, and in fact, it
Hi
Running fossil ui on any repo (using 1.29 and 1.30), all the CSS looks
disabled and the file link fails to work - no treeview or flat view.
Any ideas on how to fix?
Roy
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On 2015-02-17 23:43, Richard Hipp wrote:
I have switched the default Fossil repo over to using the San
Francisco Modern skin. Everybody seems to think it looks a lot
better, and I agree.
I like the look, but why the fixed width? I like the flexible width of
the original skin more.
Roy
Hi Richard
On 22/01/2015 22:41, Richard Hipp wrote:
Running fossil ui on any repo (using 1.29 and 1.30), all the CSS looks
disabled and the file link fails to work - no treeview or flat view.
Any ideas on how to fix?
No ideas off-hand, since nobody else is seeing this problem. Do you
On Monday 29 Dec 2014 06:30:58 Richard Hipp wrote:
Unfortunately, there is no way to do this for every check-in all at once.
You would have to go through and create separate tags for each check-in.
There is probably a way to script this. But it would be better to change
the names in git prior
On Monday 16 Mar 2015 12:07:58 Richard Hipp wrote:
On 3/16/15, Richie Adler richiead...@gmail.com wrote:
After the latest upgrades, I've been unable to see the timeline graphs if
I
have more than 36 items in the timeline. The space for the graph remains,
but
nothing is drawn.
The
On Tuesday 03 Mar 2015 16:22:40 Richard Hipp wrote:
On 3/3/15, Warren Young w...@etr-usa.com wrote:
Is there a good reason that “fossil mv” and “fossil rm” must be followed
by
OS-level mv and rm commands? I miss the behavior of Subversion which made
these into a single step.
When I
Hi List!
When importing a git fast import file, the master branch is silently
changed to trunk, to match the fossil default.
However, when exported back out the reverse conversion does not apply.
This is not good, because fossil is effectively re-writing history.
But what is worse is that the
On 09/02/2017 15:06, Joerg Sonnenberger wrote:
> On Thu, Feb 09, 2017 at 01:47:43PM +0000, Roy Marples wrote:
>> Hi List!
>>
>> In fossil I have this: branch-1.7, tag-1.2
>> But when I export I get this: branch_1_7, tag_1_2
>>
>> Why is the name mangled li
On 10/02/17 17:52, Roy Marples wrote:
> On 09/02/2017 21:42, Roy Marples wrote:
>> When importing a git fast import file, the master branch is silently
>> changed to trunk, to match the fossil default.
>> However, when exported back out the reverse conversion does not apply.
&
On 10/02/2017 19:10, Joe Mistachkin wrote:
>
> Roy Marples wrote:
>>
>> fossil import --rename-master trunk
>> fossil export --rename-trunk master
>>
>
> As a matter of my personal preferences and taste, I really like the
> idea of NOT doing "
On 13/02/17 01:01, Roy Marples wrote:
> 1) add an option to (or to not) export tags. The git default is not to,
> I'm tempted to make this the fossil default as well. See *.
This is wrong. Git has no such option.
> 2) maintain a file of tags so we only export tags generated at the
>
Hi List
So git fast-export only exports anointed tags - they usually have a comment.
Fossil tags don't have comments.
This is slightly problematic for a bridge. Because we add all tags to
the fast-export file they will overwrite tags at the other end. As such,
the git repos that sync to the git
On 13/02/17 01:23, Roy Marples wrote:
> On 13/02/17 01:01, Roy Marples wrote:
>> 1) add an option to (or to not) export tags. The git default is not to,
>> I'm tempted to make this the fossil default as well. See *.
>
> This is wrong. Git has no such option.
>
>> 2)
On 13/02/2017 06:47, Artur Shepilko wrote:
>> * no more silent renaming of master vs trunk [1]
>
> "fossil import --rename-trunk" already allows a choice for a Fossil
> branch name to receive Git's "master" branch.
> A bug was missed in src/import.c:~567 if( fossil_strcmp(z,
> "master")==0 ) z
On 13/02/2017 09:49, Roy Marples wrote:
>>> * tag comments are imported and exported [2]
>>
>> ?? How does one enter a tag comment from the Fossil command line or
>> this is an import/export only feature?
fossil tag add --comment "A tag test comment&q
On 13/02/2017 10:42, Jan Nijtmans wrote:
> 2017-02-13 4:50 GMT+01:00 Roy Marples:
>> 3 has now been implemented in the roy-export branch.
>> Turned out to be quite easy. A database rebuild is required though as an
>> extra field has been added to the tagxref table.
>
On 13/02/2017 11:12, Jan Nijtmans wrote:
> 2017-02-13 12:09 GMT+01:00 Roy Marples:
>> Is the value displayed in the timeline?
> Yes
>> I'm also unsure about overloading the meaning of tag value . the ui
>> indicates it can be set via the command line s
Hi List!
I have a few repos which I sync to git. However, one of them I noticed
is no longer syncing tags. The fossil repo is here:
https://roy.marples.name/projects/dhcpcd
Using fossil-1.37
fossil export --git dhcpcd.fossil > dhcpcd.export
git init dhcpcd-git
cd dhcpcd-git
git fast-import
Hi List!
In fossil I have this: branch-1.7, tag-1.2
But when I export I get this: branch_1_7, tag_1_2
Why is the name mangled like so? Surely the original names should be
preserved.
Roy
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
Exporting tags using fossil-1.37 I see this in the resultant import:
tagged by
whereas is should be
tagged by Roy Marples <r...@marples.name>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-s
On 09/02/2017 14:39, Roy Marples wrote:
> Exporting tags using fossil-1.37 I see this in the resultant import:
>
> tagged by
>
> whereas is should be
>
> tagged by Roy Marples <r...@marples.name>
Patch attached to fix this.
Roy
Export tag comitter.
---
On 09/02/2017 21:42, Roy Marples wrote:
> When importing a git fast import file, the master branch is silently
> changed to trunk, to match the fossil default.
> However, when exported back out the reverse conversion does not apply.
>
> This is not good, because fossil is effecti
On 26/03/2017 22:19, Joerg Sonnenberger wrote:
On Sun, Mar 26, 2017 at 07:49:30PM +0200, Tomasz Konojacki wrote:
For someone with a different background, there is *nothing* nice about
fossil dumping thousands of lines to the terminal. In fact, I think it
scares off newbies who only used git
35 matches
Mail list logo