On 8/3/2015 3:24 PM, Warren Young wrote:
After making this mistake, I know I'm supposed to move the bad commit to
a hidden branch
Who supposes this, and why do you take their opinion as normative?
When a commit to Fossil causes a problem, I've seen drh move it to a
branch (usually not hidden
On 7/27/2015 6:58 AM, Luca Ferrari wrote:
Hi,
this can be goofy, but is there a way to instrument fossil to create a
new branch from the current one instead of having to specify it?
So something like:
$ fossil branch new MYBRANCH
instead of
$ fossil branch new MYBRANCH trunk
I didn't
On 5/17/2015 7:45 PM, Andy Goth wrote:
http://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg20586.html
I found another consequence. This affects the finfo command.
Test case from before:
f init x.fossil
mkdir x
cd x
f open ../x.fossil
touch file1 file2
f add *
f commit -m 1
echo
On 8/3/2015 3:24 PM, Warren Young wrote:
On Aug 3, 2015, at 1:31 PM, Andy Goth andrew.m.g...@gmail.com wrote:
Usually I don't bother, especially if there have been check-ins since
the error was committed.
Wouldn’t a better solution to that problem be a continuous integration
system, so you
On 7/31/2015 9:55 AM, John L. Poole wrote:
The Wiki Headers and Footers are not under any versioning control or
history, correct?
As far as I can tell, that's right. The only versions you get to pick are:
1. Contents of the text edit widget (Apply Changes to select)
2. Current settings
The same for me. I always use mv as, I guess, add/remove destroys the
history of changes.
Re syncing with the file system, I find it ok as it is. Usually, I move
files using IDE when coding, and then find missing ones while trying to
commit. For me 'mv' works ok with the exception that when I
On 8/3/2015 3:37 PM, Warren Young wrote:
On Aug 3, 2015, at 12:49 PM, Andy Goth andrew.m.g...@gmail.com wrote:
On 8/3/2015 2:01 AM, Michai Ramakers wrote:
On 3 August 2015 at 01:22, Matt Welland mattrwell...@gmail.com wrote:
I've no idea if fossil mv now behaves exactly like mv.
indeed, it
Thus said Andy Goth on Mon, 03 Aug 2015 17:47:33 -0500:
(by the way, why does the URL say config when the command is
technically named configuration?)
This is due to fossil's least unambiguous command matching, any
unambiguous length of /configuration will work:
On Mon, Aug 3, 2015 at 9:04 PM, Ross Berteig r...@cheshireeng.com wrote:
And then, there will be fresh set of edge cases with subtly different
behavior on Windows. And for that matter, do all versions of
Unix-descendents mv have the same quirks at the edges?
IMHO, fossil does a remarkable
On 04/08/15 00:34, Ross Berteig wrote:
On 8/3/2015 11:49 AM, Andy Goth wrote:
On 8/3/2015 2:01 AM, Michai Ramakers wrote:
On 3 August 2015 at 01:22, Matt Welland mattrwell...@gmail.com wrote:
I've been using (and advising others to use) addremove because
fossil mv
behavior did not match Unix
On 7/16/2015 11:12 PM, Andy Bradford wrote:
Thus said Andy Bradford on Thu, 16 Jul 2015 20:56:57 -0600:
Maybe rather than doing a pull, you could deconstruct both
repositories, put the extracted artifacts into the same place,
fabricate a manifest that somehow merges the
On 8/3/2015 11:49 AM, Andy Goth wrote:
On 8/3/2015 2:01 AM, Michai Ramakers wrote:
On 3 August 2015 at 01:22, Matt Welland mattrwell...@gmail.com wrote:
I've been using (and advising others to use) addremove because fossil mv
behavior did not match Unix mv. The differences were confusing. I've
On 8/3/2015 2:01 AM, Michai Ramakers wrote:
On 3 August 2015 at 01:22, Matt Welland mattrwell...@gmail.com wrote:
I've been using (and advising others to use) addremove because fossil mv
behavior did not match Unix mv. The differences were confusing. I've no idea
if fossil mv now behaves
On 7/28/2015 9:18 PM, Warren Young wrote:
On Jul 28, 2015, at 9:32 AM, Gour g...@atmarama.net wrote:
split commit within one file
in smaller chunks when one forgets to ’safe often, commit often’ or
simply wants to divide single commit into several ones?
That said, it would be spiffy to have
On Aug 3, 2015, at 1:08 PM, Andy Goth andrew.m.g...@gmail.com wrote:
On 7/28/2015 9:18 PM, Warren Young wrote:
On Jul 28, 2015, at 9:32 AM, Gour g...@atmarama.net wrote:
split commit within one file
it would be spiffy to have a “fossil ci —cherrypick” option
...it's a bad idea...each
On 3 August 2015 at 21:31, Andy Goth andrew.m.g...@gmail.com wrote:
Many times I've created files, modified existing files to reference
them, tested, and committed, only to later discover I forgot to add the
newly created files to the repository.
After making this mistake, I know I'm supposed
Many times I've created files, modified existing files to reference
them, tested, and committed, only to later discover I forgot to add the
newly created files to the repository.
After making this mistake, I know I'm supposed to move the bad commit to
a hidden branch and try again. Usually I
Thus said Andy Goth on Mon, 03 Aug 2015 13:40:39 -0500:
diff'ing shouldn't require a common ancestor. You're thinking of
merging. merge's -baseline option lets you explicitly pick the common
ancestor, which could be either trunk's initial empty check-in.
Yes, you're right, I was
On 3 August 2015 at 21:08, Andy Goth andrew.m.g...@gmail.com wrote:
On 7/28/2015 9:18 PM, Warren Young wrote:
On Jul 28, 2015, at 9:32 AM, Gour g...@atmarama.net wrote:
split commit within one file
in smaller chunks when one forgets to ’safe often, commit often’ or
simply wants to divide
grr...
On 3 August 2015 at 21:50, Michai Ramakers m.ramak...@gmail.com wrote:
FWIW, I try to have small commits here; occasionally when unrelated
changes have been made in a single file, I simply use the word 'and'
in the commit-message, and that's about it. I agree that manually
On 1 August 2015 at 17:46, Michai Ramakers m.ramak...@gmail.com wrote:
Hello,
I was wondering what you generally do for directory trees in motion -
use add/rm or mv ? And: the benefit of fossil having a concept of
'moved file/dir' is that the user can trace ancestry crossing
moves/renames
On Aug 3, 2015, at 1:31 PM, Andy Goth andrew.m.g...@gmail.com wrote:
Many times I've created files, modified existing files to reference
them, tested, and committed, only to later discover I forgot to add the
newly created files to the repository.
Yup, been there. :)
After making this
On Aug 3, 2015, at 12:49 PM, Andy Goth andrew.m.g...@gmail.com wrote:
On 8/3/2015 2:01 AM, Michai Ramakers wrote:
On 3 August 2015 at 01:22, Matt Welland mattrwell...@gmail.com wrote:
I've no idea if fossil mv now behaves exactly like mv.
indeed, it does not.
Any plans to bring them in
23 matches
Mail list logo
