Andy Bradford amb-fos...@bradfords.org
writes:
Fossil is also very light when it comes to cloning. What about clone,
make a private branch in your clone (to avoid accidental syncing), do
your experimental work and when done, either merge into trunk (or
wherever) or displose of
Very briefly from the phone: about 6 months ago i looked into the simplest
such action i could think of - erasing the top-most checkin (from there one
could keep erasing one step back at a time). It turns out that undoing the
deltification, crosslinking and similar work performed by any routines
Stephan Beal sgb...@googlemail.com writes:
Very briefly from the phone: about 6 months ago i looked into the simplest
such action i could think of - erasing the top-most checkin (from there one
could keep erasing one step back at a time). It turns out that undoing the
deltification,
On Tue, Jul 15, 2014 at 9:37 AM, Gour g...@atmarama.net wrote:
Afaik, there was some talk inthe past about having some kind of hg-like
bundle which could be sent via email applied...
At least from the web UI, Fossil can create patch files from commits.
As best I can determine from a
On Tue, Jul 15, 2014 at 7:48 AM, Stephan Beal sgb...@googlemail.com wrote:
Very briefly from the phone: about 6 months ago i looked into the simplest
such action i could think of - erasing the top-most checkin (from there one
could keep erasing one step back at a time). It turns out that
The problem is mainly, iirc, the deltification. Arbitrary blobs may become
deltas of arbitrary others (conceptually unrelated), and undoing that is
painful.
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity and
typos.
On Jul 15, 2014 7:58 PM, Ron W
See below... (sorry, no workstation until Internet gets connected)
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity and
typos.
On Jul 15, 2014 9:56 PM, Andreas Kupries andre...@activestate.com wrote:
On Tue, Jul 15, 2014 at 12:47 PM, Stephan Beal
Hello,
the topic was already discussed several times in this mailing list, but
I wonder what is the obstacle for Fossil to provide ability to
shun/forge single branch(es), iow. whether it because it is, somehow,
against Fossil's design or there are some implementation-wise reasons?
I've started
0.02$ never really understood why people feel they need private branches. A
little public humility once in a while helps make us better developers ☺
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity and
typos.
On Jul 14, 2014 6:40 PM, Gour g...@atmarama.net wrote:
Stephan Beal sgb...@googlemail.com writes:
0.02$ never really understood why people feel they need private branches. A
little public humility once in a while helps make us better developers
First of all some code is simply too explorative by nature when one
experiments with some new things
The desire for this ability, to sync or purge specific branches, has many
possible motives - only one of which is hiding something :)
Having the ability to push, remove and create private branches on a
individual basis would make it much easier to use fossil for a gatekeeper
based build system.
11 matches
Mail list logo
