also sprach Johan Herland <johan@xxxxxxxxxxx> [2010.02.19.1000 +1300]: > Take a look at the (relatively) new notes feature. (See the > jh/notes series in 'pu' and various recent discussions on this > mailing list.) Git notes probably won't satisfy the exact > requirements you list above, but it _does_ tackle some parallel > issues (e.g. how to maintain a tree that is not checked out, > storing metadata associated with Git objects, etc.). If you take > a step back and reconsider your original problem, you might find > that it's solvable by using commit notes. > > For example, you could add a simple note to each blob that has > been reviewed, on the refs/notes/reviewed notes ref. You could > then write a simple script (using "git notes list") that lists all > blobs (i.e. files) without a corresponding note in > refs/notes/reviewed. I am aware of notes, but so far I stayed away from them, simply because it seems hackish to represent tag trees as text when dealing with a tool that is essentially all about trees and refs. Can I use notes to append information to blobs and trees, or just commit objects? -- martin | http://madduck.net/ | http://two.sentenc.es/ "without music, life would be a mistake." - friedrich nietzsche spamtraps: madduck.bogus@xxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html