On Wed, 2013-02-06 at 00:36 +0100, Stefan Sperling wrote:
> I agree it's a bug. The state of items not in the changelist shouldn't
> affect commit of items in the changelist. Please file a bug so that
> someone will take a look at it eventually! Thanks :)
> Please don't forget to include a link to
On 06.02.2013 07:21, Branko Čibej wrote:
> Given all the above, I think we should find a way to warn users --
> with a one-line note in the header of the diff output, for example? --
> about the cases where the two-parameter diff could be ambiguous
> (which, I believe, is when both parametrs are WC
On Wed, Feb 06, 2013 at 07:21:04AM +0100, Branko Čibej wrote:
> Given all the above, I think we should find a way to warn users -- with
> a one-line note in the header of the diff output, for example? -- about
> the cases where the two-parameter diff could be ambiguous (which, I
> believe, is when
On Wed, Feb 06, 2013 at 12:41:05PM +0100, Branko Čibej wrote:
> One other option would be, as was noted elsewhere in this thread, to
> invent a new subcommand for tree comparisons, keeping only the
> historical differences feature in "svn diff".
>
> That would solve the ambiguity, but it would (a)
On Wed, Feb 6, 2013 at 6:23 AM, Stefan Sperling wrote:
> On Wed, Feb 06, 2013 at 12:41:05PM +0100, Branko Čibej wrote:
>> One other option would be, as was noted elsewhere in this thread, to
>> invent a new subcommand for tree comparisons, keeping only the
>> historical differences feature in "svn
Thanks, that's what I meant to ask. :S
On Tuesday, February 5, 2013 4:35:19 PM UTC-6, Dave Huang wrote:
> On 2/5/2013 4:09 PM, Thorsten Schöning wrote:
> > Guten Tag Hector Magnanao,
> > am Dienstag, 5. Februar 2013 um 19:29 schrieben Sie:
> >
> >> Thanks, I guess my question wasn't so clear
Hi, how can I find out all tickets that were released with a given shipment? I
have a terrible time finding out specific details of changes.
Thank you so much!
Anne
http://mail-archives.apache.org/mod_mbox/subversion-announce/201212.mbox/%3CCADkdwvR7+MSca9ci8CX6EMML3vMV0EmGKhcssJuCTw=ubkf...@mail
The best way is the CHANGES file (the one you link to). We aren't
very vigilant about backdating the 'milestone' field in the issue
tracker (from 1.8.0 to 1.7.*) when we backport a fix to an earlier
release.
Anne Moroney wrote on Wed, Feb 06, 2013 at 11:53:26 -0500:
> Hi, how can I find out all t
In CHANGES, revision numbers refer to
http://svn.apache.org/viewvc/subversion/ and #1234 numbers to
http://subversion.tigris.org/issues/show_bug.cgi?id=1234
Daniel Shahaf wrote on Wed, Feb 06, 2013 at 18:58:50 +0200:
> The best way is the CHANGES file (the one you link to). We aren't
> very vigil
Hi Daniel!
1.So the issue numbers I think I understand. It thus seems you are saying that
it is impossible to easily see them 'all', right? I would have to individually
copy paste the number as a suffix of url for bug.cgi?=id=xxx, right?
2.For the revision numbers, is there any way I can
On Wed, Feb 6, 2013 at 12:30 PM, Anne Moroney
wrote:
> Hi Daniel!
> 1.So the issue numbers I think I understand. It thus seems you are saying
> that it is impossible to easily see them 'all', right? I would have to
> individually copy paste the number as a suffix of url for
> bug.cgi?=id=x
Anne Moroney wrote on Wed, Feb 06, 2013 at 12:30:00 -0500:
> Hi Daniel!
> 1.So the issue numbers I think I understand. It thus seems you are saying
> that it is impossible to easily see them 'all', right? I would have to
> individually copy paste the number as a suffix of url for
> bug.cgi
On 2/2/13 1:51 AM, "Daniel Shahaf" wrote:
>Matt Hargett wrote on Sat, Feb 02, 2013 at 02:04:06 +:
>> To parallel the additions of --include-externals to the 'commit' and
>>'ls'
>> commands, I would also like to propose adding the option to the 'diff'
>> command. I just tested latest trunk and
13 matches
Mail list logo
