Yes, this would be a serious problem for us, as well.
On Wed, Mar 16, 2011 at 1:04 AM, Michael Richter ttmrich...@gmail.com wrote:
The
ticket http://fossil-scm.org/index.html/tktview/305143bd876f693f446f78d12dbef143c46eec58 is
moving into show-stopper territory for me. I'm trying to share a
On Wed, Mar 16, 2011 at 1:04 AM, Michael Richter ttmrich...@gmail.com wrote:
The
ticket http://fossil-scm.org/index.html/tktview/305143bd876f693f446f78d12dbef143c46eec58 is
moving into show-stopper territory for me. I'm trying to share a
repository's code through fossil to fossil non-users.
Any thoughts on a feature to take a diff from a local fossil repo and
email it to someone, who can then put it in their stash? Something like
this:
fossil mail -r 23234234 zeds...@zedshaw.com
Which would send a patch from current to the -r revision to me. I could
then save the attachment and
On Mar 16, 2011, at 5:09 PM, Zed A. Shaw wrote:
Any thoughts on a feature to take a diff from a local fossil repo and
email it to someone, who can then put it in their stash? Something like
this:
fossil mail -r 23234234 zeds...@zedshaw.com
...and as a side-effect allow binary diffs to be
On Wed, Mar 16, 2011 at 11:30 AM, Michael Richter ttmrich...@gmail.comwrote:
OK, this is the sequence I've tried on my main workstation (Ubuntu 10.04):
1. Delete all fossil-scm.org cookies.
2. Close my browser (Chrome 10.0.648.134).
3. Re-open my browser.
4. Go to fossil-scm.org.
5.
Ok, I think I found the solution.
The submodule must be integrated by using
fossil open --nested
That's not documented, but I'm happy there's a solution.
From: tr...@tekwissusa.com
Sent: Tuesday, March 15, 2011 3:39 PM
To: fossil-users@lists.fossil-scm.org
Subject: [fossil-users]
Wow, didn't know about that either. For your original question, the command is
not extract but export. As specified, it just creates the files, which don't
then contain any marker that they came from fossil.
Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
On 03/16/11 00:37, Dmitry Chestnykh wrote:
I figured out why no one is explaining to me how to specify
which client certificate to use when connecting with https: Because
fossil doesn't support it yet. :)
You're right :-)
On Wed, Mar 16, 2011 at 3:41 PM, Joshua Paine jos...@letterblock.com wrote:
For your original question, the command
is not extract but export. As specified, it just creates the files, which
don't then contain any marker that they came from fossil.
Sorry, export dumps the repository in
On Wed, Mar 16, 2011 at 5:08 PM, Jan Danielsson
jan.m.daniels...@gmail.com wrote:
I need to read up on ~/.fossil and _FOSSIL_ though to see if there's
any risk of accidental information leak when pushing/pulling. The
question is if the client key should be stored in the database, or if
it's
On Mar 16, 2011, at 6:11 PM, Ron Wilson ronw.m...@gmail.com wrote:
Sorry, export dumps the repository in git-fast-export format, for the
purpose of exporting commits from Fossil to git (or other VCS that can
import git-fast-export format).
Oops--thanks for the correction. I must have been
On Wed, Mar 16, 2011 at 6:41 PM, Joshua Paine jos...@letterblock.com wrote:
Oops--thanks for the correction. I must have been having flashbacks to my SVN
days.
Surprisingly, fossil won't export a copy of the files without repository
info. Closest thing
is the zip command, which will create
I was peeking around and looked in the Log. I found a record of 2
artifacts representing my latest attempt to attach a file to a ticket.
Perhaps the attachments are just not being shown?
I did recheck the changes I made to the view ticket page, but I have
not made changes to the time line
13 matches
Mail list logo
