Dave Sann writes:
> Having a clean history with complete/logical features is recommended.
> However, in development branches we can make many small commits and
> the history may not be clean. That's fine, as long as we clean the
> history before merging into master.
You can also try to keep your
A good answer if anyone has this issue:
Having a clean history with complete/logical features is recommended.
However, in development branches we can make many small commits and
the history may not be clean. That's fine, as long as we clean the
history before merging into master.
This is where in
Not directly clojure related - but input needed
I have master
I have mybranch
I have a bunch of commits on mybranch.
I can create an attributed patch with "git format-patch master". This
includes all commits on the branch, including merges and updates from
master.
I can create an unattributed
Thanks for the patch! Hang tight, during the work on AOT compilation
I've been revisiting whether or not I can bundle the functionality of
genclass right into AOT compilation - I think I can, yielding a much
streamlined process.
At that point, I'll have some syntax for adorning defns with m
Rich,
I submitted a patch that adds support for exposing protected fields
inherited indirectly through the super class in gen-class. No problem
if it's unwanted, but would be good to know either way. Suppose the
original message should've had "patch" in the subject line; it's
"exposing ancestra
