:^:^/(trunk|branches)(/.*|$)$]
As a user, I'd prefer to see keywords rather than unusual
characters to designate special syntax. For example, I would
prefer [glob:/tags/*/private] and [regex:/tags/.*/private] to
[*:/tags/*/private] and [^:/tags/.*/private].
--apb (Alan Barrett)
representation than a void*?
Alan Barrett wrote:
[theory]
Alan, Brane specifically asked about practice not theory.
I was trying to point out that the "On which platform ..."
question appeared to be based on the incorrect assumption that
NULL macro would always expand to a void
to an implementation-defined null pointer constant;
and ..."
[2] ISO 9899:1999 section 6.3.2.3 paragraph 1: "An integer
constant expression with the value 0, or such an expression cast
to type void*, is called a null pointer constant."
--apb (Alan Barrett)
groff, but mandoc is more fussy about errors
in the input.
--apb (Alan Barrett)
etc. See section
3.2 of RFC 6838 <http://www.rfc-editor.org/rfc/rfc6838.txt> for the
requirements for vnd.* types.
--apb (Alan Barrett)
to anything. With notation like "%(f1)"
there's already a widespread convention of using "%%" to represent
a "%" character that does not introduce an expnsion.
--apb (Alan Barrett)
col2, col3 FROM temp_foo;
DROP TABLE temp_foo;
COMMIT;
--apb (Alan Barrett)
s on a single line using a as a
command delimiter. Implementations are permitted, but not
required, to support this extension.
--apb (Alan Barrett)
orks on NetBSD:
$ printf 'foo\nbar\nbaz\n' | sed -ne '/foo/,/baz/ { /bar/p
}'
--apb (Alan Barrett)
re is --tunnel-user going to
come from?
It comes from the .ssh/authorized_keys file, in a context
that is associated with exactly one ssh key (the "ssh-rsa
..." part); this would be the same place that previously had
"--tunnel-user=danielsh".
--apb (Alan Barrett)
cal unix IDs, but in most cases those strings
would not have been valid unix user names on the server host.
Perhaps it would be a good first step to add examples to
the documentation, showing how the admin can use "Full Name
" in the svn:author field, with all the common
access methods.
--apb (Alan Barrett)
ight?
As a user, I want to see the 'Ufilename' report.
Perhaps ' filename' would be more accurate? That way the output is
still clear that "Nothing happened".
Or 'ufilename' (lowercase u), for "updated but nothing really changed".
--apb (Alan Barrett)
ight?
As a user, I want to see the 'Ufilename' report.
However, if updating to an intermediate revision would have produced
conflicts, then updating to the final revision (which undoes the
changes) should not produce conflicts.
--apb (Alan Barrett)
maintainable.
I expect that changes on the subversion side could help (as you
have mentioned, adding more properties, or clearly documenting one
or more suggested ways of providing structure inside svn:author,
or both), but I still hold the opinion that your pain is caused at
least as much by FishEye as by svn.
--apb (Alan Barrett)
they no longer match.
If your third party tools can't extract the unique ID from
svn:author = "Display Name " then perhaps the
problem lies at least as much in your third party tools as in
subversion.
--apb (Alan Barrett)
another account and
password that I have to remember.
--apb (Alan Barrett)
^/dir/subdir/file exists in revision
5, but ^/dir is deleted in revision 6, then I'd like "svn log -v
-q -r6 ^/dir/subdir/file@5" to print
r6 | author | timestamp
Changed paths:
D /dir
instead of
svn: File not found: revision 6, path '/dir/subdir/file'
--apb (Alan Barrett)
s good for
choosing between "subdir/file" and "subdir.old/file". You still need a
tiebreaker of last resort after all that.
--apb (Alan Barrett)
t not to touch anything outside the
".svn" directory (or wherever metadata is kept)?
--apb (Alan Barrett)
client
decides to upgrade the working copy to a format that the other client
doesn't support. This gets even worse when working copies are shared by
multiple users (which happens a lot more often than I would like).
--apb (Alan Barrett)
x27;s limitations.
> In my world, I would probably just ask the submitter to retransmit the
> patch using some other mail software.
I have sometimes taken patches from web pages where communicating with
the author is not easy. But svn doesn't have to solve this problem; we
have external tools for patching and editing.
--apb (Alan Barrett)
tation copies
context lines from the patch or from the input file. Changing the
implementation to copy context lines from the input file would therefore
not be an incompatible change.
--apb (Alan Barrett)
ed.
On the other hand, I think it would be reasonable to have a configurable
way of allowing specified environment variables to be passed to hook
scripts.
--apb (Alan Barrett)
xcept when an enclosing heading
* has the :hover property.
*/
.sectionlink { display: none; }
.heading:hover .sectionlink { display: inline; }
/* HTML */
This is a heading
[[paragraph symbol]]
Text.
--apb (Alan Barrett)
after a few seconds when I actully wanted to read
the text in the tooltip, but on the subversion.apache.org web site I am
pleased that the unwanted tooltip disappears after a while.
--apb (Alan Barrett)
On Wed, 18 Nov 2009, Stefan Sperling wrote:
> On Wed, Nov 18, 2009 at 08:47:51AM +0200, Alan Barrett wrote:
> > On Mon, 16 Nov 2009, Stefan Sperling wrote:
> > > 5) Hunks are only applied if they do not overlap with any other hunk.
> > Other patch implementatio
ch at the same location in the input file, not about
how to choose between multiple locations in the input file that
could all be matched by the same hunk.
--apb (Alan Barrett)
, but appears to
match traditional pre-unidiff behaviour.
--apb (Alan Barrett)
tch assistant or conflict resolution tool might
want to offer the option of splitting a hunk into two or more
smaller hunks and re-trying each smaller hunk. "git add --patch"
offers something like this in a different context (getting ready
to commit a subset of the changes to a file).
--apb (Alan Barrett)
29 matches
Mail list logo
