search

grayed / bsd-upstreaming

Collaboration for upstreaming BSD-specific patches to upstream projects
ISC License
0 stars 0 forks source link

Flat directory structure? #2

Open krytarowski opened 8 years ago

krytarowski commented 8 years ago

I'm proposing a flat directory structure with git patches inside them. 1 file = 1 patch

For example:

qt5-qtbase/openbsd-0000-fix-A.txt qt5-qtbase/pkgsrc-0000-fix-aaa.txt mono/pkgsrc-0000-fix-123.txt

etc

grayed commented 8 years ago

I want to distinguish easily between patches being worked on and patches (ready to be) sent upstream. We could: a) discard the idea above; b) use flat structure and rename files when they become ready (based on your proposal); c) move files became ready to a different directory (current structure); d) something better.

Any ideas?

krytarowski commented 8 years ago

Maybe track ready files with github issues "[patch-name] Ready to upstream"

grayed commented 8 years ago

I'm afraid this won't match the "easily" word: my idea is that you could just look at file name/path and see if it needs your attention. Going to Issues page is an extra step I try to avoid. Maybe I'm too lazy. :)

I'm not opposed to plain structure, it actually matches the "less steps is good" idea, since going through directories means doing extra operations as well (faster than Github navigation, but still)... And renaming file is as much good as moving it to another folder.

Say, what if we'll name patches as "cur-foo.patch" for WIP and "ready-foo.patch" for sent ones? IMHO, the final word should after @noldensystemelektronik here, as he does most of work here. :)

krytarowski commented 8 years ago

I like to split code from meta-affairs like ready-to-upstream. But I'm up to what is easier for you.