Maybe it was the addition of the revision field? Matt.
On Oct 6, 3:16 pm, Joep Suijs <[email protected]> wrote: > Hi guys, > > Something seems to have changed... > Until now, I always regenerated all samples, copied them to the sample > directory of my working copy. This does replace many samples, but the > commit only selected files that actually changed. > This time however, commit wanted to update all files - many of which > are unchanged (like the one in this test-commit). > I reverted most of the files before commit, but this is error-prone. > > Any idea why this has changed? And how are we going to handle this? > Just commit all files (this is the easiest and least risk of errors)? > > Joep > > 2011/10/6 <[email protected]>: > > > > > Revision: 2803 > > Author: jsuijs > > Date: Thu Oct 6 12:02:23 2011 > > Log: test-commit > >http://code.google.com/p/jallib/source/detail?r=2803 > > > Modified: > > /trunk/sample/16f73_random.jal > > > -- > > You received this message because you are subscribed to the Google Groups > > "jallib" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/jallib?hl=en. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
