Skip to content

Conversation

@arielf212
Copy link
Contributor

@arielf212 arielf212 commented Apr 11, 2025

closes #126

Please read the commit messages, especially the last one:

Do note that if you used the absorb.fixupTargetAlwaysSHA option (or its cli equvalient),
you will see the commit hash instead.

I don't think its interesting enough to fix (maybe this is even the intended behaviour?)

You decide!

This was done sine they are not really helpful to the avarage user,
and take up precious line space that will be used in later commits for better stuff :)
This is more readble by the avarage user, still usable in the git CLI when copy-pasting and saves us a metric ton of precious line space :)
Do note that if you used the absorb.fixupTargetAlwaysSHA option (or its cli equvalient),
you will see the commit hash instead.

I don't think its interesting enough to fix (maybe this is even the intended behaviour?)

You decide!
Copy link
Owner

@tummychow tummychow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for the record, i'm fine with the functionality here but likely won't merge it until after #175 . large prs get first dibs on landing so they don't get stuck in rebase hell

let drain = slog_term::FullFormat::new(decorator).build().fuse();
let drain = slog_term::FullFormat::new(decorator)
// Don't write a timestamp, as requested in #126
// I am currently running git absorb myself, I know what time it is :)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no self-explanatory comments please. anyone who wants to know why we did this can blame it

@blairconrad
Copy link
Contributor

@arielf212 I notice that you haven't been active in this PR for a bit.
It seems that my (extensive) changes to the logging caused the conflicts with your contribution. Sorry about that. I'd be happy to try to resolve them, if it's not stepping on your toes.

Copy link
Contributor

@blairconrad blairconrad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't want to take a PR away from someone, but it seems this one is stuck. I have an alternative implementation for the log-formatting which I think provides a better result, and I've applied it to a conflict-free branch. If there's interest, I can incorporate most of these changes and get a fix moving by the weekend.

let drain = slog_term::FullFormat::new(decorator)
// Don't write a timestamp, as requested in #126
// I am currently running git absorb myself, I know what time it is :)
.use_custom_timestamp(|_| Ok(()))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

clever, but leaves an extra space at the beginning of each output line

@tummychow
Copy link
Owner

sure, i'll take an alternate pr for this if you've got one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Alternative output format when printing the created fixup commits

3 participants