On 12/5/06, Johannes Schindelin [EMAIL PROTECTED] wrote:
Hi,
On Tue, 5 Dec 2006, Erik Sandberg wrote:
http://lilypondwiki.tuxfamily.org/index.php?title=Development_with_GUB
Great! I noticed that this site runs mediawiki. Any chance to get the
LilyPond extension installed?
Also, there is
Johannes Schindelin wrote:
Hi,
On Tue, 5 Dec 2006, Graham Percival wrote:
# Updated but not checked in:
# (will commit)
#
# modified: .gitignore
# modified: Documentation/topdocs/NEWS.tely
...
This means that you do have modifications in those files. Could you please
try
Johannes Schindelin wrote:
It would be nice to have an accompanying tutorial introduction to
contributing with git that just goes over the following steps (in their
git equivalent):
cvs co blah blah (which I simply copy and paste from savannah anyway)
while (true) {
cvs update
Hi,
On Wed, 6 Dec 2006, Mats Bengtsson wrote:
Johannes Schindelin wrote:
It would be nice to have an accompanying tutorial introduction to
contributing with git that just goes over the following steps (in their
git equivalent):
cvs co blah blah (which I simply copy and
Hi,
On Wed, 6 Dec 2006, Graham Percival wrote:
Johannes Schindelin wrote:
Hi,
On Tue, 5 Dec 2006, Graham Percival wrote:
# Updated but not checked in:
# (will commit)
#
# modified: .gitignore
# modified: Documentation/topdocs/NEWS.tely
...
This
cvs co blah blah (which I simply copy and paste from savannah anyway)
while (true) {
cvs update // get changes that happened overnight
vi foo/bar/baz.txt // or whatever editing commands you do
make; make web // or whatever testing commands you do
cvs update
Johannes Schindelin escreveu:
The nice thing for me about Git: you never lose anything. Unless you say
git prune (in which case you really should know what you are doing), you
do not lose (committed) data.
Now, I promised to tell you what to do if all the files seem modified. Did
you
Hi,
On Wed, 6 Dec 2006, Han-Wen Nienhuys wrote:
Johannes Schindelin escreveu:
The nice thing for me about Git: you never lose anything. Unless you say
git prune (in which case you really should know what you are doing), you
do not lose (committed) data.
Now, I promised to tell you
Johannes Schindelin escreveu:
The thing is: it is so darned convenient. In 99% of calling git diff you
do not have a modified staging area. It is still fresh, and all your
changes are in the working directory only.
Then you can say
$ git diff
to see what you have changed. (Since Git
Han-Wen Nienhuys wrote:
I think it would be more logical to show those diffs as part of
git-status and perhaps git-commit, eg.
git-commit --dry-run commitoptions
shows the diff of what would be committed
git-status --diff
shows diffs of modified files in the working tree.
Hi,
On Wed, 6 Dec 2006, Han-Wen Nienhuys wrote:
I'm not saying git-diff should be inconvenient, but rather that it gives
a newbie more confidence if
git commit --dry
shows the diff of the change that he just introduced
Okay. But you mean
$ git commit --dry file1 file2...
or
$ git
Johannes Schindelin escreveu:
shows the diff of the change that he just introduced
Okay. But you mean
$ git commit --dry file1 file2...
or
$ git commit --dry -a
Well, --dry would be usable both with -a and file1, file2.
I agree with Jakub that --diff might be a better name, but it
Hi,
On Wed, 6 Dec 2006, Han-Wen Nienhuys wrote:
Johannes Schindelin escreveu:
Or, you use the script git-hunk-commit.bash which I posted. Which
reminds me: I wanted to rewrite it for you so it is more
non-brand-new-bash friendly.
:)
that's really nice, but actually recording
Jan Nieuwenhuizen wrote:
John Mandereau [EMAIL PROTECTED] writes:
I expect to be able to send a patch within a week or so. I'm slow
because I'm a bit busy and I have very little programming experience.
In that case, do you have something done already? If you have
translation updates,
---BeginMessage---
On Tuesday 05 December 2006 10:33, you wrote:
Monk Panteleimon escreveu:
For my information, would you include the stem as a single grob with the
notehead? That is what I would expect, since slightly different stems are
always attached to a slightly different notehead.
John Mandereau [EMAIL PROTECTED] writes:
Btw, the tutorial node names are fully translated and the tutorial is
polished (I pushed that a few days ago).
Ok, thanks. We may want to merge then and use my silly
build-html-docs-twice solution. Or was that reverted now, Han-Wen?
Jan.
--
Jan
Jan Nieuwenhuizen escreveu:
John Mandereau [EMAIL PROTECTED] writes:
Btw, the tutorial node names are fully translated and the tutorial is
polished (I pushed that a few days ago).
Ok, thanks. We may want to merge then and use my silly
build-html-docs-twice solution. Or was that reverted
Canorus is still in alpha phase. Version 1.0 is planned for the end of
the next year and should implement all of the NoteEdit features. Many
exotic features are there though (like multiple viewports on the same
score, scripting language and plugins support, support for harmonic
function markings,
What's the exact command for pushing stuff to git? I mean, the command
that I should use, with lilypond, not [EMAIL PROTECTED] like
it says in the tutorial. :)
My savannah username is gpercival, which is different from my computer
username (gperciva), in case that matters.
Cheers,
-
I finally succeeded in building Canorus on my Gentoo box, though I haven't
had time to play with it yet.
Some issues:
1) It claims it needs Qt 4.1, but it actually needs 4.2. (Build will fail
on a missing header with 4.1.)
2) I had to modify some of the cmake-generated makefiles to add the -lutil
Werner LEMBERG wrote:
well, it is using a priority field, which can have multiple values
for a single grob type.
Aah, if I understand you correctly, I can write
\override foo #'outside-staff-priority = #1
\override bar #'outside-staff-priority = #2
\override foo
If a user wants the symbol to be positioned at an absolute
offset from its Y-parent, they can just set
outside-staff-position to () in addition to setting Y-offset.
Sorry, outside-staff-priority, not outside-staff-position.
This doesn't work. I tried
\once \override DynamicText
Try something like
git push [EMAIL PROTECTED]/srv/git/lilypond.git
/Mats
Graham Percival wrote:
What's the exact command for pushing stuff to git? I mean, the
command that I should use, with lilypond, not
[EMAIL PROTECTED] like it says in the tutorial. :)
My savannah username is
well, it is using a priority field, which can have multiple values
for a single grob type.
Aah, if I understand you correctly, I can write
\override foo #'outside-staff-priority = #1
\override bar #'outside-staff-priority = #2
\override foo #'outside-staff-priority =
24 matches
Mail list logo
